Re: #555: frame synchronization

On Mon, Jul 21, 2014 at 3:27 PM, Michael Sweet <> wrote:
> Generally I think this is unnecessary - HTTP depends on "reliable" transport (TCP as defined) so we probably don't need this for frames generally.

To me the most obvious advantage is not about data corrupted/lost by
transport, but in rapid detection of buggy http2 implementations in

> It could be useful for HEADERS/PUSH_PROMISE for tracking which version of the header table is in use (see my recent posting on the Cost Analysis thread), but that all depends on how hard we want to avoid dropping connections when things go wrong...

I don't think we want to avoid it at all; in case of a frame desync
due to a buggy peer the most reliable recovery mechanism is reset and
retry, isn't it?


Received on Monday, 21 July 2014 13:38:19 UTC