On Thu, 2013-03-21 at 19:41 +0530, Asankha C. Perera wrote: > Hi All > > Should we internally update the socket timeout on the pooled connection > when one calls PoolEntry.updateExpiry()? > > Also, I am trying to fix a corner case bug, where we submit a request > through the HttpAsyncRequester.execute(). There is a connection in the > pool, which is later found to have timed out - shouldn't the system > automatically get a new connection and attempt the send? >
Hi Asankha HttpAsyncRequester presently provides only a bare bone functionality right now. It would certainly make sense to make it more capable. I just probably will not be able to work on it until 4.4. By the way, did you have a chance to try out 4.3? Cheers Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
