Re: [quicwg/base-drafts] Possible HoL blocking due to co-mingling payload and metadata (header) address space. (#1606)

[Lucas Pardue <[e-mail]>]

@martinthomson thanks for the explanation feedback. Since it took me time to digest what you said let me echo back my interpretation: for a more loosely coupled interaction mode, the use of DATA frames prevents random access to the QUIC stream because there'll be HTTP/QUIC frame headers at unknown locations. 

One approach, therefore, might be to carry bodies directly in STREAM frames, which starts to sound like GQUICs approach. The difference being that we might avoid use of stream ID's directly and use some other token to correlate headers and bodies.

In a partial reliability world, with the above design lost STREAM frames are ok. They result in HTTP body gaps, that can be skipped or repaired (say by byte-range request as @grmocg suggests). We implement a design like this today in our multicast QUIC prototype.

-- 
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/1606#issuecomment-408018646