mirror/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2024-12-22 15:57:07 +00:00
Code Issues Releases Wiki Activity
restic/vendor/github.com/cenkalti/backoff
History
Alexander Neumann 3eea555155 Add dependency cenkalti/backoff
2017-10-14 15:56:25 +02:00
..
.gitignore Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
.travis.yml Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
backoff.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
backoff_test.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
context.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
context_test.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
example_test.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
exponential.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
exponential_test.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
LICENSE Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
README.md Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
retry.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
retry_test.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
ticker.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
ticker_test.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
tries.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00
tries_test.go Add dependency cenkalti/backoff 2017-10-14 15:56:25 +02:00

README.md

Exponential Backoff GoDoc Build Status Coverage Status

This is a Go port of the exponential backoff algorithm from Google's HTTP Client Library for Java.

Exponential backoff is an algorithm that uses feedback to multiplicatively decrease the rate of some process, in order to gradually find an acceptable rate. The retries exponentially increase and stop increasing when a certain threshold is met.

Usage

See https://godoc.org/github.com/cenkalti/backoff#pkg-examples

Contributing

  • I would like to keep this library as small as possible.
  • Please don't send a PR without opening an issue and discussing it first.
  • If proposed change is not a common use case, I will probably not accept it.