Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
websocket-stream
websocket-stream is a non-blocking RFC-6455 wrapper for TcpStream on POSIX-like kernels. I don't do enough Windows development to care about implementing it for that configuration. Feel free to send me a pull request if you want to take the time to implement Windows sockets as well.
It achieves it's non-blocking state by setting the O_NONBLOCK
flag on the
stream's file descriptor. Aside from the system calls, the entire API is
memory safe.
Why another Websocket Thing in Rust?
There are a lot of Websocket libraries out for Rust right now, but they all force the same model of server design on the library user. Most implement Websockets by creating a thread for each connection to read, and one to write. Mainly to overcome Rust's blocking as default IO implementation. This is wonderful, unless your server is expected to handle lots of concurrent connections for long periods of time. Context switching between 200k threads will absolutely kill any gains you get by having separate read and write operations.
Example Usage
extern crate "websocket-stream" as wss;
use WebSocketStream;
use ;