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?
Right now we hardcode
async-tlsas 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?