Re: [quicwg/base-drafts] Priority in QUIC Transport (#104)

[Patrick McManus <[e-mail]>]

conceptually I agree it works best between the app and transport. But then again conceptually the app and transport are intertwined in quic so talking about it doesn't feel radically out of place. If we don't want transport to do anything special (i.e. retransmissions) based on it, then it does become a matter of implementation and api fodder rather than something to worry about in base-drafts I suppose.

but again, seeing huge runs of data of the same resource with maximum frame sizes (obviously buffered in tcp buffers) is a really common quality-of-implementation fail mode for h2 and it has lead to a number of "performance evaluations" claiming h2 performs worse than 1. So if a new protocol can help with that footgun, its only to its own benefit I would think.

One way to do that is to drag priorities down into the transport.

-- 
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/104#issuecomment-270990219