Michael Becke wrote : > Sounds like a reasonable plan. If you haven't already I would > recommend looking at HttpClient.executeMethod(). It has a little bit > of extra code for handling proxies and for opening the connection.
I've seen it, but I think this means I have to use on HttpClient for each user, cause it's using it's private HttpState to execute the request... If there was a HttpClient.executeMethod(HttpState state, HttpConnection conn), that would work, but in my case that's why I first did the "hack" in the nightly (ex multiclient), to avoid multiple clients (memory / perf...). Am I right ? > Also, be sure to release the connections after you use them. You can > use either HttpMethod.releaseConnection() or > HttpConnection.releaseConnection() to ensure each connection is > released. Are you sure I have too ? It seems that in the end HttpMethodBase executeMethod (line 957), there's a call to release the connection used. Thanx for your advice, I'm going into it now. Aurelien Pernoud --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
