So is it that connections never be reused. I am sorry if I am repeating my question. My earlier mails also i was asking at what stage a connection is reused by HttpClient. And does the connection get reused. I got a reply to log the information. But when i run my coe with just two connections even then the connections are not being reused. Could please help me in this aspect. I want to knwo whether HttpClient ever reuses the connections, if it uses then at what stage. Thanks in advance.
On Thu, 29 Dec 2005 Oleg Kalnichevski wrote : >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: [EMAIL PROTECTED] > > > > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > >--------------------------------------------------------------------- > > >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] >
