template< class DynamicBuffer, class ReadHandler> void-or-deduced async_read( DynamicBuffer& buffer, ReadHandler&& handler);
This function is used to asynchronously read a message from the stream. The function call always returns immediately. The asynchronous operation will continue until one of the following is true:
This operation is implemented in terms of one or more calls to the next
and is known as a composed operation. The program
must ensure that the stream performs no other reads until this operation
Upon a success, the input area of the stream buffer will hold the received
message payload bytes (which may be zero in length). The functions
websocket::stream::got_text may be used to query
the stream and determine the type of the last received message.
During reads, the implementation handles control frames as follows:
websocket::stream::control_callbackis invoked when a ping frame or pong frame is received.
Because of the need to handle control frames, read operations can cause
writes to take place. These writes are managed transparently; callers can
still have one active asynchronous read and asynchronous write operation
pending simultaneously (a user initiated call to
websocket::stream::async_close counts as a write).
A dynamic buffer to hold the message data after any masking or decompression has been applied. This object must remain valid until the handler is called.
The handler to be called when the read operation completes. Copies will be made of the handler as required. The function signature of the handler must be:
void handler( error_code const& ec; // Result of operation );
Regardless of whether the asynchronous operation completes immediately
or not, the handler will not be invoked from within this function.
Invocation of the handler will be performed in a manner equivalent