Especially when a URI connection fails, we may not want
to use a constant-length retry-delay, but rather one
that grows with each failure. This could be achived by
providing a factor which is raised to the power of the
number of retries, that is multiplied by the 'initial'
retry-delay.
That is, delay = base_delay *
(backoff_factor^consecutive_retries).
A typical value for base_delay might be 1 minute; a
typical factor for backoff_factor might be 2. Then
retries would occur after 1 minute, then another 2,
then another 4, then another 8, etc.
When a site is really down for many hours (or a day or
more), this sort of patience could be better than
considering a URI a failure after only an hour or two
of retrying.
Gordon Mohr
Network/Protocols
None
Public
|
Date: 2007-03-14 01:28
|
|
Date: 2004-06-03 22:08 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2004-06-03 22:08 | gojomo |
| close_date | - | 2004-06-03 22:08 | gojomo |
| assigned_to | johnerik | 2004-06-03 19:09 | gojomo |
| assigned_to | nobody | 2004-03-30 23:34 | gojomo |
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use