Defaults are another good topic of discussion. I personally think that there should be some reasonable, finite default value for every timeout. (I also think that max conns should be unlimited by default.) But the first order of business is deciding exactly how we want the existing timeout parameters to behave, and where the current implementation falls short with respect to the desired end state.
On Tue, Nov 13, 2018 at 2:50 PM Gary Gregory <garydgreg...@gmail.com> wrote: > > Hi Ryan, > > I'm glad you've brought this up as I've often considered this and have been > asked about it, in general, and for our apps at work. > > In the end, a lot of users say something like "I do not want the default > behavior to wait forever, that looks like the app is hanging. I want some > timeout but I do not really care that it is exactly 30 seconds, it just > needs to tell me it's hopeless to wait longer than 30 seconds or so." > > OTOH, I am certain there are cases where an app wants more precise control > and I do think it is important to know that this timeout must be less than > another or that this one is added to that one from the user's POV... > > IOW, I'd love to see all of this clearly coded or at least clearly > documented as a first step. > > Gary --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
