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
Right now we hardcode async-tls as a hard dependency via async-tungstenite. This is not ideal for every use case, especially because it transitively depends on ring, which brings its fair share of licensing troubles.
We should expose these options to library users via separate feature flags. As the default rendezvous server doesn't actually use wss we could easily define the default as no TLS, same as async-tungstenite.
Alternatively we could even possible disable wss support for now. AFAIU it was only added for webasm support, which is now gated behind different feature flags, right?
The text was updated successfully, but these errors were encountered:
The included TLS features are only required for wss connections to the mailbox
server which not required by the protocol and only really useful for wasm
builds.
Closes#216
The included TLS features are only required for wss connections to the mailbox
server which not required by the protocol and only really useful for wasm
builds.
Closes#216
Right now we hardcode
async-tls
as a hard dependency via async-tungstenite. This is not ideal for every use case, especially because it transitively depends onring
, which brings its fair share of licensing troubles.We should expose these options to library users via separate feature flags. As the default rendezvous server doesn't actually use wss we could easily define the default as no TLS, same as async-tungstenite.
Alternatively we could even possible disable wss support for now. AFAIU it was only added for webasm support, which is now gated behind different feature flags, right?
The text was updated successfully, but these errors were encountered: