Re: [quicwg/base-drafts] Make using static table and Huffman encoding in QPACK opt-in (#3622)

[Lucas Pardue <[e-mail]>]

> This will in fact affect the first flight of requests if the client does not receive server's SETTINGS frame fast enough. That does sound like a problem, but it will be eventually fixed when we fix #3086, so I'm not particularly concerned.

hat-off:  I would push back against introducing a performance regression in v1 that *might* possibly be fixed in v2

> I am not sure how that kind of profile would look in practice. The reason I am filing this for v1 is that in general, you can add complexity as an opt-in, but opting out of it does not really work.

CoAP has done a pretty decent job and seems to have traction.

One way is to profile things is to create a new Application Protocol e.g. "h3-lite" or whatever, that can completely profile away all the features that are deemed as too much overhead. One could then make sweeping changes such as rewriting the message exchanges to use an ASCII-HEADERS frame that just carries verbatim headers.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3622#issuecomment-623607334