Header continuation

[martinthomson]

@grmocg suggested that his header compression (#2) would include the ability to continue header blocks across frames. We should track this as a separate issue.

Important consideration is the way that header blocks mutate session state (for header compression). Interleaving of continued header frames will cause issues if we don't address this.

We should also consider whether this is a general facility or not.

[grmocg]

I believe we should fix this by declaring that, if there is a continuation
happening, no new headers frame is allowed to be sent until the
continuation is finished.
It just gets too difficult to deal with otherwise.

On Mon, Mar 11, 2013 at 1:26 PM, martinthomson notifications@github.comwrote:

@grmocg https://github.com/grmocg suggested that his header compression
(#2 #2) would include the
ability to continue header blocks across frames. We should track this as a
separate issue.

Important consideration is the way that header blocks mutate session state
(for header compression). Interleaving of continued header frames will
cause issues if we don't address this.

We should also consider whether this is a general facility or not.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/50
.

[mnot]

To clarify - you mean that no headers frame on a different stream can be sent?

[grmocg]

yes.

It isn't the only possible solution, but it is relatively simple and it
seems like it should be a rare enough case...
-=R

On Mon, Mar 18, 2013 at 2:14 AM, Mark Nottingham
notifications@github.comwrote:

To clarify - you mean that no headers frame on a different stream can be
sent?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/50#issuecomment-15040712
.