-
Notifications
You must be signed in to change notification settings - Fork 974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Add experimental QUIC support. #862
Conversation
Since `QuicConfig::dial` consumes the context we better keep a copy in the future and subsequently the stream muxer to make sure it is not dropped prematurely. For listening it is assumed that the listener outlives the connections, hence we do not copy the context from a listening stream into each stream muxer.
Why not |
Because most of quinn's types are |
@twittner This has now been fixed, if I understand correctly. Furthermore, we can also use the |
We can likely place the expected remote cert by an ImOnline key or whatever into |
QUIC is not only a transport, but also a multiplexer. Does this protocol handle that? |
/// task executor | ||
executor: Exec, | ||
/// RSA private key | ||
private_key: Vec<u8>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should not put secret keys in a Vec
.
@demimarie-parity This is an old branch that wasn't even finished and that is kept alive just for reference (to get inspiration from). There's no point in commenting. |
Continuation of #563, based on picoquic-rs.
cc: @bkchr