Hi Gael, Sorry your original message got left on my back-burner, I try to keep up with the few HttpClient questions that appear on this list but I've been doing badly lately.
The multiple HttpClient's/one manager will work, but you should be able to have a single HttpClient, single connection manager and just an independant HttpState instance for each session. All the cookies and other persistent information is stored in the HttpState and it uses significantly less memory than a full HttpClient. We added executeMethod(HttpMethod, HttpState) style methods to HttpClient just for this purpose. You may also want to pop over to the HttpClient-dev list and ask for opinions on the best way to achieve that there as I know there are a few people using HttpClient as a proxy style server there. It also sounds like a doc I should add to the website so it would be good to gather opinions. Regards, Adrian Sutton, Software Engineer Ephox Corporation www.ephox.com -----Original Message----- From: news [mailto:[EMAIL PROTECTED] Behalf Of Gael Marziou Sent: Wednesday, 30 July 2003 6:25 AM To: [EMAIL PROTECTED] Subject: Re: [HttpClient) Simple vs. MultiThreadedHttpConnectionManager within a servlet Sorry, discard my previous message, I took a closer look at the doc and decided that I will use a client per session and a common shared MultiThreadedHttpConnectionManager. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
