W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1998

Re: HTTP features w/ low 'implemented' and 'tested'

From: Koen Holtman <koen@win.tue.nl>
Date: Mon, 30 Mar 1998 21:05:24 +0200 (MET DST)
Message-Id: <199803301905.VAA07495@wsooti20.win.tue.nl>
To: Jeffrey Mogul <mogul@pa.dec.com>
Cc: http-wg@cuckoo.hpl.hp.com
Jeffrey Mogul:
>

[rlgray@raleigh.ibm.com:]
>    Imagine the request times out, or a shark eats the trans-Atlantic
>    cable the object is being transfered over, or whatever.  Now, I
>    have to close the connection to the client, who recieves a
>    truncated object with no indication of an error (until he tries to
>    use it and finds it is corrupted).  There is no possiblity of
>    reporting what the problem is either.
>    
>Maybe I'm missing something, but this seems like an ideal scenario
>for "Chunked".

Hmm, I always thought it would be possible to generate a tcp-level
error (connection abort?) instead of closing the connection to the
client in the normal way.  Wouldn't that tell the client that
something is wrong?

Koen.
Received on Monday, 30 March 1998 11:08:08 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:33:14 EDT