ezsockets
ezsockets copied to clipboard
High-level declarative API for building WebSocket Clients and Servers in Rust 🦀
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: SendError [session.rs:99:33](https://github.com/gbaranski/ezsockets/blob/master/src/session.rs#L99) ```rust /// Calls a method on the session pub async fn call(&self, params: P) { self.calls.send(params).unwrap(); } ````...
closes #10
Adding configurable socket through SocketConfig could allow users to change the default heartbeat duration, timeout and message. It is already implemented on the client side. For tungstenite: https://github.com/gbaranski/ezsockets/blob/932eb743949cc8f9612dc61f98bbcd6c364c3b54/src/server_runners/tungstenite.rs#L63-L109 and for...
Currently you can only reject a connection after the websockets backend has accepted the connection. This means clients will always see 'connected' -> 'disconnected' events even if their connection request...
I had trouble understanding this crate's API because a lot of the names overlap with each other. After lots of reading the source code... Suggestions: - `SessionExt` -> `SessionHandler` -...
This is a secondary PR to further reduce tokio tasks