- From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
- Date: Wed, 12 Dec 2018 09:00:49 -0500
- To: Ian Swett <ianswett@google.com>
- Cc: Roberto Peon <fenix@fb.com>, Ryan Hamilton <rch@google.com>, Jana Iyengar <jri.ietf@gmail.com>, Mike Bishop <mbishop@evequefou.be>, HTTP Working Group <ietf-http-wg@w3.org>, Lucas Pardue <lucaspardue.24.7@gmail.com>, IETF QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>, Kazuho Oku <kazuhooku@gmail.com>
On Tue, Dec 11, 2018 at 09:02:01PM -0500, Ian Swett wrote: > TLDR: If the focus is on shipping v1 and making sure we don't introduce > premature optimizations into HTTP/3, I thInk we should seriously consider > moving PUSH and the existing priorities to an extension. The EOS DATA frame and HTTP prioritization and push promises are not equivalent. One is simply fiddling with the way data is framed and is not visible to the application. The others are HTTP/2's primary features. - Dmitri.
Received on Wednesday, 12 December 2018 14:01:16 UTC