Some possible alternatives:
* Only do the isStale check if the connection has been sitting in the pool for a configurable amount of time. I'm guessing we could choose a value here between 5 and 30 seconds without any significant change in behavior, that is to say, connections won't go stale in less than 20-30s.
Not agreed here. A connection can become stale at virtually any time due to the underlying IP stack implementation, or misbehaving servers. As seen in the wild.
* Perhaps the "isStale" check is unnecessary for methods that can
simply repeat themselves, for example, GET, HEAD, OPTION, TRACE. For those methods, we could allow a "retry" to fix the problem. For methods such as POST and PUT, however, the isStale is probably
an essential check.
Sounds reasonable to me.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
