huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Minor fix to transport protocol spec

This commit is contained in:
Andrew Stanton-Nurse 2017-01-18 09:12:34 -08:00
parent 7a27c5891c
commit 8b6c25ad86
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
specs/TransportProtocols.md
View File

@ -26,7 +26,7 @@ The WebSockets transport is unique in that it is full duplex, and a persistent c
The WebSocket transport is activated by making a WebSocket connection to `[endpoint-base]/ws`. Upon doing so, the connection is fully established and immediately ready for frames to be sent/received. The WebSocket OpCode field is used to indicate the type of the frame (Text or Binary) and the WebSocket "FIN" flag is used to indicate the end of a message.
Establishing a second WebSocket connection when there is already a WebSocket connection associated with the Endpoints connection is not permitted and will fail with a `400` (Bad Request) status code.
Establishing a second WebSocket connection when there is already a WebSocket connection associated with the Endpoints connection is not permitted and will fail with a `409 Conflict` status code.
## HTTP Post (Client-to-Server only)
@ -165,4 +165,4 @@ The encoding will be as follows, as a list of binary digits in hex (text in pare
0x01 0x02 (body)
```
This transport will buffer incomplete frames sent by the server until the full message is available and then send the message in a single frame.
This transport will buffer incomplete frames sent by the server until the full message is available and then send the message in a single frame.