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 Sep 12, 2023. It is now read-only.
The two first libraries are written in RUST that are not intended (because the exported 'dll' and 'lib' are large in size). The others have to be reviewed and implemented and then the proper one would be selected as the transmission library for WOLF.
The text was updated successfully, but these errors were encountered:
The last two libraries MsQuic and lsquic were reviewed. MsQuic is supported only for windows and Linux platforms currently. MsQuic may be built with other configurations, but they are not to be considered officially supported.
lsquic is built on all platforms windows, osx, ios, android, and Linux. Also, it is possible to remove or add the option of http3 header wrapping.
It seems lsquic is the best available library for QUIC implementation at the moment.
MsQuic has been developed based on OpenSSL while lsquic supports boringSSL.
Generally speaking, I prefer boringSSL but QT and most of Wolf's dependencies are using openSSL, so we don't have any choice to go with MsQuic.
We need to develop w_quic_client and w_quic_server under namespace of wolf::stream
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It has been decided to use QUIC as the transmission protocol in WOLF. There are plenty of libraries that implemented this protocol such as:
The two first libraries are written in RUST that are not intended (because the exported 'dll' and 'lib' are large in size). The others have to be reviewed and implemented and then the proper one would be selected as the transmission library for WOLF.
The text was updated successfully, but these errors were encountered: