W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: Getting to Consensus: CONTINUATION-related issues

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Fri, 18 Jul 2014 18:20:50 +0000
To: Martin Thomson <martin.thomson@gmail.com>
cc: Michael Sweet <msweet@apple.com>, Nicholas Hurley <hurley@todesschaf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <5657.1405707650@critter.freebsd.dk>
In message <CABkgnnW3-FkS33PA90LRbCXM9AoUf9177eV9UrkLVaAcT9BC-A@mail.gmail.com>
, Martin Thomson writes:
>On 18 July 2014 10:07, Michael Sweet <msweet@apple.com> wrote:
>> Nothing has been said about a required rollback capability, and I can't find any mention of rollback on the linked wiki page either.
>
>Say you have a block of headers that you need to encode for sending.
>You discover that you exceed the limit only after performing the
>encoding up to the point that you exceed the limit.  At that point,
>you can't send the block.  And all the changes that have been applied
>to the header table need to be backed out.

I don't think it says anywhere that you cant *send* the block, but if
you do, you should expect it to get rejected.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Friday, 18 July 2014 18:21:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:09 UTC