Mike, Why do you think that providing an ability to enumerate of HTTP connection would break this pattern?
I think that adding this functionality could be okay depending on the use. My worry is that it opens up a whole host of possible invalid uses. This was not the concern I was trying to convey in my previous statement though. I intended to discourage major connection configuration (timeout, send buffer, etc.) as part of the connection retrieval/release process. I think this should be handled by the methods/HttpClient.
What good would that make? You can always get HttpConnectionParams from the HttpConnection. Am I missing something?
I was looking at this from the perspective of Fabio's question. He needs to be able to set the SO_TIMEOUT on a per method execution basis. Since he doesn't have direct access to the connection being used, my though was that HttpClient could handle this configuration using passed in params. This is just one possible solution, I'm sure there are others.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
