Re: Final DATA frames

I don't want to derail this too much(probably too late for that), and no
one has a PR anywhere close to landing, but I do think we should start
thinking of these as potential extensions.  I disagree that they're
HTTP/2's primary features, both due to lack of use and lack of measurable
benefits years after standardization.  Push might actually benefit from
being an extension, because then potential improvements(ie: cache-digest)
could be integrated into the extension more quickly.

On the other hand, QPACK is relatively complex but we have clearer
demonstrations of it's benefit.

On Wed, Dec 12, 2018 at 9:00 AM Dmitri Tikhonov <dtikhonov@litespeedtech.com>
wrote:

> 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.
>