Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to future-based WS server. #158

Open
tomusdrw opened this issue Jun 14, 2017 · 6 comments
Open

Switch to future-based WS server. #158

tomusdrw opened this issue Jun 14, 2017 · 6 comments

Comments

@tomusdrw
Copy link
Contributor

No description provided.

@tomusdrw tomusdrw added the feat label Jun 14, 2017
@andresilva
Copy link
Member

andresilva commented Jun 15, 2017

Do you have any idea of which library to use for async websockets? tokio-tungstenite seems like a good option although I have no experience with it.

@tomusdrw
Copy link
Contributor Author

Nothing in mind, haven't done a research yet. tokio-tungstenite looks good!

@faern
Copy link
Contributor

faern commented Oct 29, 2017

I think https://crates.io/crates/websocket looks like a reasonable contestant. But did not have time to test it extensively yet.

@tomusdrw
Copy link
Contributor Author

tomusdrw commented Jul 5, 2018

Would be awesome to be able to publish HTTP and WS on the same port: http://seanmonstar.com/post/175280388657/better-http-upgrades-with-hyper

@CodeSandwich
Copy link

Another reason to switch: websocket depends on hyper 0.10, which has security issues: https://rustsec.org/advisories/RUSTSEC-2020-0008.html

@tomusdrw
Copy link
Contributor Author

https://docs.rs/soketto/0.4.1/soketto/ looks like a very good candidate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants