From 4e384f086b08e6b7be01022f4ebcab6af6758317 Mon Sep 17 00:00:00 2001 From: Mohammad Nejati Date: Tue, 11 Feb 2025 08:47:32 +0000 Subject: [PATCH] async_read_some documentation mentions how to identify message completion Closes #2969 --- include/boost/beast/websocket/stream.hpp | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/include/boost/beast/websocket/stream.hpp b/include/boost/beast/websocket/stream.hpp index f307c572..1aa47e35 100644 --- a/include/boost/beast/websocket/stream.hpp +++ b/include/boost/beast/websocket/stream.hpp @@ -2281,6 +2281,8 @@ public: Received message data is appended to the buffer. The functions @ref got_binary and @ref got_text may be used to query the stream and determine the type of the last received message. + The function @ref is_message_done may be called to determine if the + message received by the last read operation is complete. Until the operation completes, the implementation will read incoming control frames and handle them automatically as follows: @@ -2488,6 +2490,8 @@ public: Received message data is appended to the buffer. The functions @ref got_binary and @ref got_text may be used to query the stream and determine the type of the last received message. + The function @ref is_message_done may be called to determine if the + message received by the last read operation is complete. Until the operation completes, the implementation will read incoming control frames and handle them automatically as follows: