Peter Thorson

I would like to see this data set as well!

This regression from 0.8.0 has been fixed on the `develop` branch. The `socket_init` event handler is the correct place to set socket options like `TCP_NODELAY` on the already accepted socket.

Some terms from the web socket RFC. Message = message delivered via on_message to WS++ or W3C JS API. In WS++ now send() sends a message. Message payloads are sent...

Every Boost library that WebSocket++ uses is exclusively as a polyfill for the associated `std` library (or standalone Asio in the case of `boost::asio`). If you are using a well...

as an aside that might also be of interest for microcontrollers: It is possible to disable the use of exceptions (some embedded environments don't have), compression (which adds the zlib...

A fix for this has been pushed to the develop branch. That branch will be rolled up into a 0.9 release soon.

The reason that WebSocket++ does not handle keeping track of outstanding connections internally is that doing so adds overhead (requires centralized locking and potentially non O(1) data structures) which affects...

You should not get new connections after `endpoint::stop_listening` is called. Is there any chance your endpoint is multithreaded? If so there might be a race condition to investigate. Is the...

I've reviewed a bit more. Connections that are in the connecting state when stop_listening() is called will continue to the open state and have the open handler called after stop...

> Does "streaming" in this case mean HTTP responses that are not available in full at time of sending? Something like > > ```python > defer() > send_headers() > append_body("Hello,...