Stefan Fritsch <[email protected]> writes: > In any case, we need at least three values to completely define the > behaviour. IIRC I chose the initial timeout/maximum timeout over the > startup time/maximum timeout approach because it was easier to > implement. I still think it's ok, given that for normal > configurations, there is not much difference. But the "headerinit" > keyword is just a bit too cryptic for my taste.
> Do you agree that using RequestReadTimeout instead of RequestTimeout > and using a single keyword with a timeout range is more descriptive > than the current syntax? Yes, I like that better too. Dan
