W3C home > Mailing lists > Public > www-jigsaw@w3.org > May to June 1999

re:RE: max_conn and timeout

From: Yves Lafon <ylafon@w3.org>
Date: Mon, 3 May 1999 15:29:23 +0200 (MET DST)
To: Giannakopoulos Michalis <mgi@elca.ch>
cc: www-jigsaw@w3.org
Message-ID: <Pine.GSO.4.10.9905031524550.11612-100000@tarantula.inria.fr>
On Fri, 30 Apr 1999, Giannakopoulos Michalis wrote:

> >But I need to take a closer look before sending the right patch ;)
> Cool!

It is now fixed! And there was another thing to solve. The new version
will be available soon from
(Should be v1.51)

> And about the value of timeout that does not match the system property
> declared in http-server.props ?

I traced that call and the client socket is created and the timeout is set
to org.w3c.www.protocol.http.connections.timeout
However, as explained in the jdk api, it doesn't mean that the effective
conenction will be cut after this timeout, just that an exception will be
fired if a blocking operation (ie: a read) reaches this timeout.

      /\          - Yves Lafon - World Wide Web Consortium - 
  /\ /  \        Architecture Domain - Jigsaw Activity Leader
 /  \    \/\    
/    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org    
Received on Monday, 3 May 1999 09:32:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:26 UTC