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
I am implementing MoQT python package (aiomoqt) as close to the QUIC layer interface as possible, after WT session established.
The protocol handler for quic_event_received detects a new stream and the data will have QUIC stream identifier bits.
e.g., 0x405400 (uni) or 0x404100 (bidi).
Is this by design or perhaps i am not implementing some handling in my protocol. i wanted to not pass this through H3/WT as WebtransportStreamDataReceived as that seemed to introduce some difficulties for MoQT's
If i insist on staying at the QUIC layer is there an elegant .. or least gross way to get the stream identifier removed.. or i just do it
This discussion was converted from issue #566 on April 04, 2025 13:14.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am implementing MoQT python package (aiomoqt) as close to the QUIC layer interface as possible, after WT session established.
The protocol handler for quic_event_received detects a new stream and the data will have QUIC stream identifier bits.
e.g., 0x405400 (uni) or 0x404100 (bidi).
Is this by design or perhaps i am not implementing some handling in my protocol. i wanted to not pass this through H3/WT as WebtransportStreamDataReceived as that seemed to introduce some difficulties for MoQT's
If i insist on staying at the QUIC layer is there an elegant .. or least gross way to get the stream identifier removed.. or i just do it
Beta Was this translation helpful? Give feedback.
All reactions