You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DATA frame section includes some commentary on H3, frames and streams. In reviewing a PR, I made the following observations:
This seems like it can be genericised and moved somewhere else: there is no tight coupling between H3 and QUIC frame boundaries meaning a H3 frames could span many packets, or many frames could be in a single packet.
Implementations can deploy streaming strategies to any H3 frame parsing. I agree that DATA frames are the most likely, but really any frame could be larger than a packet.
Furthermore, due to varint H3 frame fields and the lack of preserved boundaries, some implementations might generate data_moved events before frame_parsed events. Cloudflare quiche does this, for example.
The DATA frame section includes some commentary on H3, frames and streams. In reviewing a PR, I made the following observations:
Originally posted by @LPardue in #274 (comment)
The text was updated successfully, but these errors were encountered: