Hi Sam,
My thought, probably not well articulated, was to add the ability to
observe and interact with the status of HttpConnections. This would
allow for classes other that the connection managers to play a hand in
the connection management. Another possibility would be to have a
HttpConnec
Hi Mike,
Using a listener seems like an interesting idea, although I don't quite
see the rationale behind it. MTCM (well, CM's in general really) seem
to be designed specifiically for this purpose: to manage http
connections. Having an observable interface to HttpConnection would
require add
Hi Sam,
I think this is definitely something that could be a useful addition to
HttpClient. Though it would be possible to add this functionality to
the MultiThreadedHttpConnectionManager (MTCM) I think I would like to
keep it separate. Partially because I think MTCM is getting a little
to c
Thanks for the reply, Mike. Is there any interest in a feature that
would close connections that have been unused for a certain amount of
time? I imagine the easiest way to implement this would be to just add
some settable parameters (set/getCloseConnectionTime) to
MultiThreadedHttpConnection
Hi Sam,
HttpClient does not do any active connection reclaiming, except when
the resources are reused. In the case of the
SimpleHttpConnectionManager the connection is never closed/reopened
unless it is required for a new method execution. The case for
MultiThreadedHttpConnectionManager is s