Open lynn2910 opened 1 year ago
ws://echo.websocket.org
No longer works. You can use ws://ws.vi-server.org/mirror
instead.
What is the reason of using websocket
instead of recommended alternative tungstenite
?
ws://echo.websocket.org
No longer works. You can use
ws://ws.vi-server.org/mirror
instead.
This address works properly, but how can I connect to wss
since I have the handshake failure ?
What is the reason of using
websocket
instead of recommended alternativetungstenite
?
Because, I use this in the crate mlua
, but the Tokio runtime can't be used a athis context.
That's why I need a websocket client that is not async
Tokio runtime can't be used a athis context
I don't remember tungstenite
(unlike tokio-tungstenite
or async-tungstenite
) to be dependent on Tokio.
Does tungstenite::client_tls match your needs?
Hello, i have an error when connecting to a secure websocket (url:
wss://gateway.discord.gg
)Error:
I declare the client with
It seems like connecting to a wss throw this error. Perhaps, when i try using "ws://echo.websocket.org", i get:
(trace:)
But the websocket doesn't initialize itself when connecting to a
wss