Return-Path: Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 64341 invoked from network); 29 Jul 2003 07:06:06 -0000 Received: from main.gmane.org (80.91.224.249) by daedalus.apache.org with SMTP; 29 Jul 2003 07:06:06 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19hOYl-0006JO-00 for ; Tue, 29 Jul 2003 09:06:11 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: commons-user@jakarta.apache.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19hOYi-0006J4-00 for ; Tue, 29 Jul 2003 09:06:08 +0200 From: Gael Marziou Subject: [HttpClient) Simple vs. MultiThreadedHttpConnectionManager within a servlet Date: Tue, 29 Jul 2003 09:06:13 +0200 Lines: 22 Message-ID: Reply-To: gael.marziou@free.fr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org X-Newsreader: Forte Agent 1.93/32.576 English (American) Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello, I am using HttpClient from a servlet which basically provides some kind of URL rewriting and reverse proxying capabilities based on the user's profile. Each session has it s own HttpClient instance in order to manage session cookies for remote back ends independently from other users. In this context, it seems to me that the MultiThreadedHttpConnectionManager is useless because multi threading is done at servlet level and so SimpleHttpConnectionManager seems a better choice to me because it's simpler and consumes less server resources. Is my understanding correct? Is there any risk in using SimpleHttpConnectionManager in this context? Thanks, Gael