forked from boostorg/beast
Update and tidy documentation
This commit is contained in:
1 parent
8607af5efe
commit
b4a8342795
26 files changed
+678
-598
No files matched your search
@@ -71,9 +71,7 @@ template<class T>
|
||||
struct is_Body
|
||||
{
|
||||
using type = std::integral_constant<bool,
|
||||
has_value_type<T>::value &&
|
||||
std::is_default_constructible<
|
||||
typename extract_value_type<T>::type>::value
|
||||
has_value_type<T>::value
|
||||
>;
|
||||
};
|
||||
|
||||
@@ -92,7 +90,7 @@ class is_Parser
|
||||
template<class U, class R =
|
||||
std::is_convertible<decltype(
|
||||
std::declval<U>().write(
|
||||
std::declval<boost::asio::const_buffer const&>(),
|
||||
std::declval<boost::asio::const_buffers_1 const&>(),
|
||||
std::declval<error_code&>())),
|
||||
std::size_t>>
|
||||
static R check2(int);
|
||||
|
||||
@@ -72,8 +72,8 @@ struct frame_info
|
||||
For asynchronous operations, the type must support the
|
||||
@b `AsyncStream` concept.
|
||||
|
||||
@note A stream object must not be destroyed while there are
|
||||
pending asynchronous operations associated with it.
|
||||
@note A stream object must not be moved or destroyed while there
|
||||
are pending asynchronous operations associated with it.
|
||||
|
||||
@par Concepts
|
||||
@b `AsyncStream`,
|
||||
@@ -1018,7 +1018,8 @@ public:
|
||||
hold all the message payload bytes (which may be zero in length).
|
||||
|
||||
Control frames encountered while reading frame or message data
|
||||
are handled automatically. Pings are replied to, pongs are noted,
|
||||
are handled automatically. Pings are replied to automatically,
|
||||
pongs are routed to the pong callback if the option is set,
|
||||
and close frames initiate the WebSocket close procedure. When a
|
||||
close frame is received, this call will eventually return
|
||||
@ref error::closed. Because of the need to handle control frames,
|
||||
@@ -1053,7 +1054,8 @@ public:
|
||||
hold all the message payload bytes (which may be zero in length).
|
||||
|
||||
Control frames encountered while reading frame or message data
|
||||
are handled automatically. Pings are replied to, pongs are noted,
|
||||
are handled automatically. Pings are replied to automatically,
|
||||
pongs are routed to the pong callback if the option is set,
|
||||
and close frames initiate the WebSocket close procedure. When a
|
||||
close frame is received, this call will eventually return
|
||||
@ref error::closed. Because of the need to handle control frames,
|
||||
@@ -1152,7 +1154,8 @@ public:
|
||||
fi.fin == true, and zero bytes placed into the stream buffer.
|
||||
|
||||
Control frames encountered while reading frame or message data
|
||||
are handled automatically. Pings are replied to, pongs are noted,
|
||||
are handled automatically. Pings are replied to automatically,
|
||||
pongs are routed to the pong callback if the option is set,
|
||||
and close frames initiate the WebSocket close procedure. When a
|
||||
close frame is received, this call will eventually return
|
||||
@ref error::closed. Because of the need to handle control frames,
|
||||
@@ -1190,7 +1193,8 @@ public:
|
||||
fi.fin == true, and zero bytes placed into the stream buffer.
|
||||
|
||||
Control frames encountered while reading frame or message data
|
||||
are handled automatically. Pings are replied to, pongs are noted,
|
||||
are handled automatically. Pings are replied to automatically,
|
||||
pongs are routed to the pong callback if the option is set,
|
||||
and close frames initiate the WebSocket close procedure. When a
|
||||
close frame is received, this call will eventually return
|
||||
@ref error::closed. Because of the need to handle control frames,
|
||||
@@ -1233,7 +1237,8 @@ public:
|
||||
the stream buffer.
|
||||
|
||||
Control frames encountered while reading frame or message data
|
||||
are handled automatically. Pings are replied to, pongs are noted,
|
||||
are handled automatically. Pings are replied to automatically,
|
||||
pongs are routed to the pong callback if the option is set,
|
||||
and close frames initiate the WebSocket close procedure. When a
|
||||
close frame is received, this call will eventually return
|
||||
@ref error::closed. Because of the need to handle control frames,
|
||||
|
||||
Reference in new issue
Block a user