Return-Path: Delivered-To: apmail-jakarta-httpclient-user-archive@www.apache.org Received: (qmail 2119 invoked from network); 29 Dec 2005 10:47:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Dec 2005 10:47:16 -0000 Received: (qmail 9901 invoked by uid 500); 29 Dec 2005 10:47:15 -0000 Delivered-To: apmail-jakarta-httpclient-user-archive@jakarta.apache.org Received: (qmail 9884 invoked by uid 500); 29 Dec 2005 10:47:15 -0000 Mailing-List: contact httpclient-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: "HttpClient User Discussion" Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-user@jakarta.apache.org Received: (qmail 9869 invoked by uid 99); 29 Dec 2005 10:47:15 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Dec 2005 02:47:15 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [80.74.144.174] (HELO uml24.umlhosting.ch) (80.74.144.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Dec 2005 02:47:14 -0800 Received: from oleg by uml24.umlhosting.ch with local (Exim 4.50) id 1ErvJ7-0002eP-EZ for httpclient-user@jakarta.apache.org; Thu, 29 Dec 2005 11:46:53 +0100 Date: Thu, 29 Dec 2005 11:46:53 +0100 From: Oleg Kalnichevski To: HttpClient User Discussion Subject: Re: Re: Does HttpClient retain connection on explicit Server termination Message-ID: <20051229104653.GA10189@uml24.umlhosting.ch> Mail-Followup-To: HttpClient User Discussion References: <20051229062806.27301.qmail@webmail55.rediffmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051229062806.27301.qmail@webmail55.rediffmail.com> User-Agent: Mutt/1.5.9i X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Thu, Dec 29, 2005 at 06:28:06AM -0000, bharathi swarajya wrote: > But does the Jakarta HttpClient create a new connection or close of this connection. Will the pooling concept come here. > As I said there is no way for HttpClient to know that the connection has been dropped by the server. So, 'stale' connections will stay in the pool unless some measures are taken to evict connections from the pool after a certain period of inactivity Oleg > > On Wed, 28 Dec 2005 Oleg Kalnichevski wrote : > >On Wed, Dec 28, 2005 at 01:17:59AM -0000, bharathi swarajya wrote: > > > ?Hi > > > > > > I have some clarification regarding the HttpCLient mechanisam. When a server explicitly sends a termination request, how does HttpClient behave. Does it still reuse such kind of connections. will that be considered as a part of the pool.Could anyone help in this. > > > > > > >The HTTP protocol does not provide a mechanism to notify the > >counterpart of the fact that the connection is about to be closed. Both > >the client and server may close the connection at any time without prior > >notice > > > >Oleg > > > > > > > > > > Thanks > > > S.S. Bharathi > > > > > > > > > On Wed, 28 Dec 2005 Oleg Kalnichevski wrote : > > > >On Tue, 2005-12-27 at 23:11 +0530, Nishant Agrawal wrote: > > > > > Thanks Oleg. > > > >... > > > > > > > > > > > > > > > -- If I send to 2 different servers (at 2 different URLs), > > > > > > > > > > -- how will implementation decide as to which manager to use, for > > > > > present key-cert combo to each server. > > > > > > > > > > -- here I assume that each different server recognizes this same client > > > > > application, by different identities. > > > > > > > > > > > > > > > > > > > > --For e.g.: > > > > > > > > > > --ClientApp has 2 keyManagers > > > > > > > > > > ---1. KeyManager_A ( key_a, certChain_a) > > > > > > > > > > ---2. KeyManager_b ( key_b, certChain_b) > > > > > > > > > > -- server_a identifies certChain_a only. > > > > > > > > > > -- server_b identifies certChain_b only. > > > > > > > > > > > > > > > > > >You have to configure different SSL contexts for these two servers. The > > > >easiest way to achieve that is to have a different key store per > > > >different identity > > > > > > > >Oleg > > > > > > > > > > > >--------------------------------------------------------------------- > > > >To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org > > > >For additional commands, e-mail: httpclient-user-help@jakarta.apache.org > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org > >For additional commands, e-mail: httpclient-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpclient-user-help@jakarta.apache.org