rberlich/estray

A testbed for the integration and performance-evaluation of Boost.Beast and Boost.Serialization

estray's Issues

Questions: client read behavior

Hi. This is not an actual issue, but didn't find another point of contact.
Trying to understand the client design.

See async_websocket_client::run():

	// We need an additional thread for the processing of incoming work items
	std::thread processing_thread (
		[this]() {
			this->m_io_context.run();
		}
	);

	// This call will block until no more work remains in the ASIO work queue
	m_io_context.run();

The client doesn't seem to use an explicit strand for serializing tasks.

• Is this still guaranteed to work?
• How is the processing_thread bound to read operations?
• Can this client send and receive messages independently?