Thanks for the reply.
When the connection will be come idle?.
Why do we need to forcefully run the separate thread to close the idle
connections like CLOSE_WAIT? OS will close these connections after some
particular amount of time if we don't run this thread?
Thanks
Ashar
Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
On Mon, Nov 07, 2005 at 01:01:58PM +0000, kunal ashar wrote:
>
> Hi,
>
>
>
> One of the HTTPClinet 2.0 Features says that
>
>
>
> Connection management support for use in multi-threaded applications.
> Supports setting the maximum total connections as well as the maximum
> connections per host. Detects and closes stale connections.
>
>
>
> This says that it detects and closes the stale connections.
>
>
> My questions is
>
>
>
> "Is closing of idle connections are automatically taken care or we need to
> implement IdleConnectionTimeoutThread to close the idle connections
> forcefully?"
>
>
Idle and stale connections are different things. Stale connections are
automatically taken care of per default, whereas idle ones are not.
Please note as well that IdleConnectionTimeoutThread is available in
HttpClient 3.0 only.
Hope this helps,
Oleg
>
> Thanks
> Ashar
>
>
>
>
>
> ---------------------------------
> How much free photo storage do you get? Store your holiday snaps for FREE
> with Yahoo! Photos. Get Yahoo! Photos
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
To help you stay safe and secure online, we've developed the all new Yahoo!
Security Centre.
