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

Catching up with changes introduced within the rust-websocket repository #1

Open
wants to merge 299 commits into
base: master
Choose a base branch
from

Conversation

JulianDroste
Copy link

@JulianDroste JulianDroste commented Apr 27, 2023

In SpaceManiac/discord-rs#181 we talked about the websocket crate version depending on an out-of-date hyper version. In the upstream project's README.md it is mentioned, that due to sluggish maintainership, maybe checking out the following crates would also be an option:

ashfordneil and others added 30 commits May 15, 2017 11:15
Make it actually useful in multi-threaded environment.
* move set_nonblocking() to server with OptionalSslAcceptor
* add test for set_nonblocking()
* add docs
Enet4 and others added 30 commits December 9, 2019 14:02
- provide a more informative message of cause
- print actual status code on StatusCodeError (resolve vi/websocat#55)
Fix response => response display message

Co-Authored-By: Peter W <[email protected]>
This other crate is being maintained, it offers better performances
(when using the `asm` feature, especially [on
AArch64](RustCrypto/hashes#97)).  It also allows
deduplicating SHA-1 crates in cargo-web.
Expose native_tls as it's needed to use your API
Remove deprecated usage of the "description" and "cause" functions
Properly gate TLS error variants in Display impl
chore(docs): remove mio async comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.