Peter Thorson

When used with asynchronous transports (Like the bundled asio transport). `send()` is an async operation which queues a message to be sent and then returns. Calling send twice in a...

The telemetry_server example uses the timer method to remain responsive while providing server pushed telemetry in a single thread. The interrupt handler is not used, but it is semantically very...

You are sending all of the data in on_message. To break it up using interrupt you need to call send in the interrupt handler. i.e. ``` on_message(...) { ... s->send(hdl,...

What is going on here is that you are seeing logs printed both by WebSocket++ core (the ones that are using your custom logger) and also messages printed by the...

you'll generally need to write some data to the socket in order to detect a disconnect. The WebSocket protocol has a ping message that you can send that can be...

For mixed TLS/non TLS clients the procedure is similar to servers. I’ll see if I can prepare a client example that handles both secure and non-secure endpoints. In the meantime...

The end of file "error" generally means the remote endpoint closed the connection without performing a WebSocket protocol closing handshake. This is forbidden by RFC 6455 in most cases and...

Can you confirm when the crash happens? You mentioned the connection completes and the issue is on first message, but the stack trace shows the library in the connection initialization...

The way to do this right now is to have two endpoints, one for secure and one for unsecure, and switch on which one you use by inspecting the address....

TCP socket level, no, but the WebSocket handshake can return HTTP headers which can be used to carry the CORS information. In your WebSocket++ validate handler, use `connection::append_header` (https://docs.websocketpp.org/classwebsocketpp_1_1connection.html#af8cb78acc61b8a3d59f6162cdba6318b) or...