BEMW currently relies on ws_stream_wasm and ws_stream_tungstenite for its websocket implementations. Both of these are licensed as unlicense which is apparently legally dubious in some countries. This crate should ideally not rely on either of those. This probably wouldn't ever be an actual issue but I think its better to get it out of the way and just make sure its all good
Problems
At the time of making this crate it was very difficult to find a websocket crate that is not tokio dependent and supported async, both in the web and native. Any new crate would have to support all that as well.
NoahShomette
commented
2 weeks ago
BEMW currently relies on
ws_stream_wasmandws_stream_tungstenitefor its websocket implementations. Both of these are licensed asunlicensewhich is apparently legally dubious in some countries. This crate should ideally not rely on either of those. This probably wouldn't ever be an actual issue but I think its better to get it out of the way and just make sure its all goodProblems
At the time of making this crate it was very difficult to find a websocket crate that is not tokio dependent and supported async, both in the web and native. Any new crate would have to support all that as well.
Crates to look into/try: