Re: [PROPOSAL] Change *attempts_timeout to be in milliseconds

2018-08-20 Thread Alan Carroll
t should > override the non-_ms > > From: Leif Hedstrom > Sent: Friday, August 17, 2018 5:59 PM > To: dev@trafficserver.apache.org > Subject: [EXTERNAL] Re: [PROPOSAL] Change *attempts_timeout to be in > milliseconds > > Meh, I see

Re: [PROPOSAL] Change *attempts_timeout to be in milliseconds

2018-08-17 Thread Zelkowitz, Evan
Hedstrom Sent: Friday, August 17, 2018 5:59 PM To: dev@trafficserver.apache.org Subject: [EXTERNAL] Re: [PROPOSAL] Change *attempts_timeout to be in milliseconds Meh, I see the PR with treating non zero values taking precedence. That works, with the somewhat odd behavior that an explicit zero

Re: [PROPOSAL] Change *attempts_timeout to be in milliseconds

2018-08-17 Thread Leif Hedstrom
Meh, I see the PR with treating non zero values taking precedence. That works, with the somewhat odd behavior that an explicit zero cannot override the old value . I think that’s fine though. I agree with amc that for 9.0.0 (current master) we should cleanup this consistently, floats seems fine

Re: [PROPOSAL] Change *attempts_timeout to be in milliseconds

2018-08-17 Thread Leif Hedstrom
As suggested elsewhere, having some new configs might be the safest transitions. We can then deprecate, and later remove, the 1s ones. They would have to take precedence, but that can be tricky to deal with as a undefined value :-/. Maybe the smallest non-zero value should be used ? — Leif >

[PROPOSAL] Change *attempts_timeout to be in milliseconds

2018-08-17 Thread evan . zelkowitz
We started seeing some problems with some of our origins/parents and we believe that if we had finer control over the attempts timeout it might help alleviate some problems. Currently all of these timeouts are in seconds, and when it comes to live streaming with 2sec fragments that granularity m