forked from boostorg/beast
Allow concurrent websocket async ping and writes:
fix #271 This modifies the websocket stream implementation's composed operations to allow caller-initiated asynchronous pings and frame/message writes to take place at the same time.
This commit is contained in:
+2
-2
@@ -320,8 +320,8 @@ operations can cause socket writes. However, these writes will not
|
||||
compete with caller-initiated write operations. For the purposes of
|
||||
correctness with respect to the stream invariants, caller-initiated
|
||||
read operations still only count as a read. This means that callers can
|
||||
have a simultaneous active read and write operation in progress, while
|
||||
the implementation also automatically handles control frames.
|
||||
have a simultaneously active read, write, and ping operation in progress,
|
||||
while the implementation also automatically handles control frames.
|
||||
|
||||
[heading Ping and Pong Frames]
|
||||
|
||||
|
||||
Reference in New Issue
Block a user