W3C home > Mailing lists > Public > www-lib@w3.org > July to September 2005

Timeout when doing a POST, connection status?

From: Tatu Saloranta <tsaloranta@gmail.com>
Date: Sat, 2 Jul 2005 18:47:00 -0600
Message-ID: <5f777058050702174772f383ae@mail.gmail.com>
To: www-lib@w3.org

I am trying to debug a problem with a protocol handler that does
fairly simple POST request/reply transactions using libwww. There is a
problem with protocol states that seems to sometimes occur when
reading of the data for POST times out (timeout is set to fairly low
value, and this often happens during load testing).

What I am wondering is what happens to the TCP connection used by the
HTTP 1.1 persistent connection (assuming one is used) on timeout: will
it get automatically closed (and new one opened next a request will be
sent)? I would assume so, since connection's state is not stable at
that point? Or if not, is there a way to force it to be discarded, to
ensure that a "fresh" new connection is first established?
(the reason timeout app uses is low has to do with the design; since
process instances are not properly multi-threaded, there's need to
avoid longer blocking)

-+ Tatu +-
Received on Sunday, 3 July 2005 01:58:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:45 GMT