DevWiki/websocket-sharp
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[Modify] Edit it

Browse Source
This commit is contained in:
sta 2016-10-30 18:15:05 +09:00
parent 7b240345e3
commit db01e9e7f7
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -432,19 +432,19 @@ For more information, would you see **[Example3]**?
#### Per-message Compression ####
websocket-sharp supports the **[Per-message Compression][compression]** extension (but doesn't support this extension with the [context take over]).
websocket-sharp supports the [Per-message Compression][compression] extension (but does not support it with the [context take over]).
As a WebSocket client, if you would like to enable this extension, you should set such as the following.
As a WebSocket client, if you would like to enable this extension, you should set the `WebSocket.Compression` property to a compression method before calling the connect method.
```csharp
ws.Compression = CompressionMethod.Deflate;
```
And then your client will send the following header in the handshake request to the server.
And then the client will send the following header in the handshake request to the server.
Sec-WebSocket-Extensions: permessage-deflate; server_no_context_takeover; client_no_context_takeover
If the server accepts this extension, it will return the same header which has the corresponding value. And when your client receives it, this extension will be available.
If the server accepts this header, it returns the same header which has the corresponding value. And this extension will be available when the client receives it.
#### Ignoring the extensions ####