Mark Verleg
Mark Verleg
@PingHGao I think this might not be the best place to get help with your problem sorry
If I understand #632 correctly, this is fixed. Indeed I am not seeing the original warning locally.
Although this is technically a valid problem, I'm going to close it because * It's been 3+ years without further interest * There is a workaround that's okay for many...
I think I'll do utf8 if it is valid, and base64 otherwise. I'll also pick base64 if primitives are requested. I considered higher bases but I think base64 will be...
Version 3.16.0 is released with bytes support for Python 3. Python 2 does not encode bytes because it does not have a bytes type (and is dead). Let me know...
As a way to address * Performance * Excessive deprecation messages I think it might be good to always try to * Parse without stripping comments if ignore_comments is None...
Released v3.16.1 with this optimization,
You're starting the server twice (`run_ws()` at the start and end of main in both examples). Perhaps it does shut down once, but gets started again? The second one never...
Maybe you could do something like this? Not sure if it's the best way... To send a message to a connection, you'd use the `Sender` object. So if you want...
I have ssl feature on in Cargo ws = { version = "0.7.9", features = ["ssl"] } So I think it's different from #238 but I don't really know