Re: HTTP features w/ low 'implemented' and 'tested'
David W. Morris (dwm@xpasc.com)
Mon, 30 Mar 1998 20:13:07 -0800 (PST)
On Mon, 30 Mar 1998, Koen Holtman wrote:
> 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?
I don't believe you can count on clients differentiating all cases and
treating the abort as an error.
Dave Morris