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
IIUC, QUIC supports both reliable streams and best-effort datagrams over the same cryptographic session established between two endpoints.
Although datagrams probably do not make sense for h3, it would still be useful if I can use h3 to share an already established QUIC session with datagram processing that could be happening concurrently. I haven't looked at h3 code very carefully, but it looks like h3 takes ownership/hides the underlying QUIC session, which would make getting datagrams a bit difficult.
@stammw following up on the Discord question.
IIUC, QUIC supports both reliable streams and best-effort datagrams over the same cryptographic session established between two endpoints.
Although datagrams probably do not make sense for
h3
, it would still be useful if I can useh3
to share an already established QUIC session with datagram processing that could be happening concurrently. I haven't looked ath3
code very carefully, but it looks likeh3
takes ownership/hides the underlying QUIC session, which would make getting datagrams a bit difficult.For example, quinn-rs exposes
Datagrams
in theNewConnection
struct, which has apoll_next()
method that would be worth exposing: https://docs.rs/quinn/latest/quinn/struct.Datagrams.html#method.poll_next.An example of how to do it would be great! Happy to chip in and contribute as well.
The text was updated successfully, but these errors were encountered: