W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2019

Re: HTTP/2 Server Push and solid compression

From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Date: Thu, 23 May 2019 07:31:20 +0300 (EEST)
To: HTTP Working Group <ietf-http-wg@w3.org>, Felipe Gasper <felipe@felipegasper.com>
CC: Alan Egerton <eggyal@gmail.com>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Message-Id: <20190523043127.2FCBEC3F35@welho-filter2.welho.com>
> Possibly … does h2 multiplexing use a separate compression context for each stream, or does it 
> funnel each message through the same context?

HPACK (Header Compression for HTTP/2) uses one context for all streams.

This is processed when HEADERS or CONTINUATION frame is received. HEADERS frame is also used when
stream is opened.

Frames on HTTP/2 are processed sequentially because it is transported over TCP. So there is
no problem with out of order access of header compression context.

/ Kari Hurtta
Received on Thursday, 23 May 2019 04:31:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:34 UTC