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
{{ message }}
This repository has been archived by the owner on Aug 18, 2020. It is now read-only.
We are currently looking for a UDP protocol capable of server side initialized sessions (i.e server push). I know HTTP/2 that runs on QUIC supports this, so QUIC must be capable of it too.
Googles quic documentation states "Streams can be created either by the client or the server". Currently I can't see this implemented with this library. Could it be?
The text was updated successfully, but these errors were encountered:
Thanks for your quick reply, ah I see the flow now.
I've skimmed your code and it looks like you have all the parts that make up a unencrypted quic implementation (Good Job!). I'll be testing both this and the other nodejs QUIC implementation quicker. It's only for a prototype at this stage to see if a protocol like this will provide benefits.
Would I be correct to assume this project 'basically' works?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are currently looking for a UDP protocol capable of server side initialized sessions (i.e server push). I know HTTP/2 that runs on QUIC supports this, so QUIC must be capable of it too.
Googles quic documentation states "Streams can be created either by the client or the server". Currently I can't see this implemented with this library. Could it be?
The text was updated successfully, but these errors were encountered: