Add this in your
[dependencies] async-tungstenite = "*"
This crate is based on tungstenite
Rust WebSocket library and provides async bindings and wrappers for it, so you
can use it with non-blocking/asynchronous
TcpStreams from and couple it
together with other crates from the async stack. In addition, optional
integration with various other crates can be enabled via feature flags
async-tls: Enables the
async_tlsmodule, which provides integration with the async-tls TLS stack and can be used independent of any async runtime.
async-std-runtime: Enables the
async_stdmodule, which provides integration with the async-std runtime.
async-native-tls: Enables the additional functions in the
async_stdmodule to implement TLS via async-native-tls.
tokio-runtime: Enables the
tokiomodule, which provides integration with the tokio runtime.
tokio-native-tls: Enables the additional functions in the
tokiomodule to implement TLS via tokio-native-tls.
tokio-rustls: Enables the additional functions in the
tokiomodule to implement TLS via tokio-rustls.
gio-runtime: Enables the
giomodule, which provides integration with the gio runtime.
WebSocket provides a message-oriented protocol, and this crate supports sending
and receiving data in messages; protocols built on WebSocket are allowed to
make message boundaries semantically significant. However, some users of
WebSocket may want to treat the socket as a continuous stream of bytes. If you
know the sending end does not place significance on message boundaries, and you
want to process a stream of bytes without regard to those boundaries, try
which builds upon this crate.