On Thu, Aug 31, 2017 at 1:00 PM Mark Hanson <mhan...@pivotal.io> wrote:
> I would have to go looking, but the key concept is that this is a bigger > problem. > > interval such as the time between retries.... > wait as in how long to wait for a response... > All time intervals should be expressed in terms of std::chrono::duration values. A value of std::chrono::duration::zero means don't wait. I would suggest that a negative time not be allowed and that some very large, MAXINT, value could take the place of "forever". There is a ticket already open and in progress to replace all time based values with std::chrono. > retry as how many times to retry after a failure > attempts as in how many times to do a thing before giving up > Set of objects as in the setRetryAttempts code which , will try a number of > servers before giving up. where n is the number, -1 equals all, and 0 means > (1 server, no retries). > If there are other examples of "iteration" then we should consider them based on what they iterate. I think the consensus on setRetryAttempts is to abolish it. -Jake
