Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Subject: Re: Timeout settings not working properly
From: Oleg Kalnichevski <olegk@apache.org>
To: HttpClient User Discussion <httpclient-users@hc.apache.org>
In-Reply-To: <49749FA7.5050201@switch.ch>
References: <DF11995D-12C2-4E22-8972-81EA36B23673@aftonbladet.se>
	 <1232374485.12412.9.camel@ubuntu>
	 <C8B920A7-358B-4E4D-A690-027BC4FE0443@aftonbladet.se>
	 <1232378830.12412.16.camel@ubuntu>  <49749FA7.5050201@switch.ch>
Content-Type: text/plain
Date: Mon, 19 Jan 2009 17:18:44 +0100
Message-Id: <1232381924.12412.21.camel@ubuntu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Mon, 2009-01-19 at 16:43 +0100, Chad La Joie wrote:
> Oleg Kalnichevski wrote:
> > Socket timeout is the maximum period of inactivity between two
> > _consecutive_ read operations. 
> 
> One issue might be that this isn't in the documentation.  What you said
> is actually different than what the documentation says.  The docs say
> it's the time the socket will *wait* for data, not the time between read
> operations, and if the method is related to the Socket.setSoTimeout
> method than that says something different still (i.e. the max amount of
> time a read operation will wait for data).
> 
> I'm not 100% sure which is actually correct, but I'm guessing probably
> the last one.
> 

Guessing does not always help. 

Oleg


---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org