W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2012

Re: Lingering Close

From: Jamie Lokier <jamie@shareable.org>
Date: Wed, 28 Nov 2012 19:36:11 +0000
To: Zhong Yu <zhong.j.yu@gmail.com>
Cc: Willy Tarreau <w@1wt.eu>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20121128193611.GB17008@jl-vm1.vm.bytemark.co.uk>
Zhong Yu wrote:
> Thanks Willy, I think I get what you mean by now. FIN should be
> initiated by server to avoid the TIME_WAIT problem. Therefore the
> half-close step is important.
> The current text makes perfect sense to me now.

That's great.  I knew about the RST problem (and waiting for data-ACK
isn't enough to solve that), but I didn't think about the client-side
TIME_WAIT problem before now.  Thanks Willy!

> Unfortunately, this lingering close process cannot be implemented on
> top of some APIs; these APIs don't do transparent lingering close upon
> close() either. But it is their fault, not the spec's.

Unfortunately because the old HTTP specs didn't mention this, it seems
to be widely believed that ordinary close is fine for HTTP, and APIs
were created with HTTP in mind to run over them with this limitation.
It's unfortunate that lingering close wasn't made clear in the earlier

-- Jamie
Received on Wednesday, 28 November 2012 19:36:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:07 UTC