commit 6a351a9315e3e94402a4d0cc563b1607a042d06c Author: David Fifield <david@bamsoftware.com> Date: Mon Apr 16 13:17:58 2012 -0700 Say that WebSocket message boundaries are not significant. --- doc/websocket-transport.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/websocket-transport.txt b/doc/websocket-transport.txt index 6b2b1e5..45de461 100644 --- a/doc/websocket-transport.txt +++ b/doc/websocket-transport.txt @@ -170,8 +170,10 @@ Considerations specific to pluggable transports Endpoints SHOULD respond to Ping frames with a single Pong frame, but nothing in this specification requires the sending of Ping frames. - Endpoints SHOULD limit the size of messages they send. All messages - SHOULD be sent in a single frame. + Message and frame boundaries are not meaningful. Received non-control + messages are concatenated, in order, to reconstruct the original + stream. Endpoints SHOULD limit the size of messages they send. All + messages SHOULD be sent in a single frame. Endpoints MUST limit the size of messages and frames that they will buffer. Upon receiving such a message (when the sum of the length of