From db01e9e7f7f27d9865a4c3e6ddad00c0f3ad4d15 Mon Sep 17 00:00:00 2001 From: sta Date: Sun, 30 Oct 2016 18:15:05 +0900 Subject: [PATCH] [Modify] Edit it --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index bf50ac9e..6227060a 100644 --- a/README.md +++ b/README.md @@ -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 ####