Return-Path: Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 14703 invoked by uid 98); 16 Jan 2003 09:06:09 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 14667 invoked from network); 16 Jan 2003 09:06:07 -0000 Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142) by nagoya.betaversion.org with SMTP; 16 Jan 2003 09:06:07 -0000 Received: (qmail 59915 invoked by uid 500); 16 Jan 2003 09:04:34 -0000 Received: (qmail 59878 invoked from network); 16 Jan 2003 09:04:34 -0000 Received: from unknown (HELO KCCXOEX10.corp.kpmgconsulting.com) (57.80.136.6) by daedalus.apache.org with SMTP; 16 Jan 2003 09:04:34 -0000 Received: from kccxoex03.corp.kpmgconsulting.com ([57.80.136.6]) by KCCXOEX10.corp.kpmgconsulting.com with Microsoft SMTPSVC(5.0.2195.4905); Thu, 16 Jan 2003 09:05:22 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: isHttp11 and HTTP/1.0 servers Date: Thu, 16 Jan 2003 09:04:43 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: isHttp11 and HTTP/1.0 servers Thread-Index: AcK9PcTVjiT0HhaEQiSgw06EirEw5AAAOV2Q From: "Kalnichevski, Oleg" To: "Commons HttpClient Project" X-OriginalArrivalTime: 16 Jan 2003 09:05:22.0534 (UTC) FILETIME=[6683F060:01C2BD3E] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N There's no design flaw. I was wrong. There's one connection manager per = client Oleg PS: HttpClient *should* be thread safe. The question is how thoroughly = we have tested it -----Original Message----- From: Ortwin Gl=FCck [mailto:ortwin.glueck@nose.ch] Sent: Thursday, January 16, 2003 10:01 AM To: Commons HttpClient Project Subject: Re: isHttp11 and HTTP/1.0 servers Kalnichevski, Oleg wrote: > Well, the trouble here is that in most cases the consumer of the > HttpClient should not mess around with the pool of connections, as > the same connection can be reused by different instances of the > HTTPClient class (please correct me if I err). The sole purpose of > the HttpClient is to abstract the end user from the complexity of > having to deal with connections. That is why I would rather see HTTP > version flag within HttpClient scope. But, of course, there are > different ways of seeing things >=20 > Oleg Possible design flaw: ConnectionManagers should not be shared among HttpClient instances. But=20 the HttpClient should rather be thread safe (is it at the moment?). -- To unsubscribe, e-mail: = For additional commands, e-mail: =