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
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
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
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
Hi All,
I'd like to clarify a point about HttpClient that I do not fully
understand. How/when does the actual connection to a server close? I
understand that MultiThreadedHttpConnectionManager (and possibly
SimpleConnectionManager as well) will keep the connection alive and
reuse it for
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
