That's priced at **US$15**. I think that your $15 makes this project more better and accelerated, Thank you!
That's priced at **US$15**. I think your $15 makes this project more better and accelerated, Thank you!
## Supported .NET framework ##
## Supported .NET framework ##
@ -305,6 +311,12 @@ If you override the `OnMessage` method, it is bound to the server side `WebSocke
In addition, if you override the `OnOpen`, `OnError` and `OnClose` methods, each of them is bound to each server side event of `WebSocket.OnOpen`, `WebSocket.OnError` and `WebSocket.OnClose`.
In addition, if you override the `OnOpen`, `OnError` and `OnClose` methods, each of them is bound to each server side event of `WebSocket.OnOpen`, `WebSocket.OnError` and `WebSocket.OnClose`.
The `WebSocketService.Send` method sends a data to the client of the current session to the WebSocket service.
The `WebSocketService.Sessions` (its type is `WebSocketSharp.Server.WebSocketSessionManager`) property provides some functions for the sessions to the WebSocket service.
The `WebSocketService.Sessions.Broadcast` method sends a data to all client of the WebSocket service.
#### Step 3 ####
#### Step 3 ####
Creating an instance of the `WebSocketServer` class.
Creating an instance of the `WebSocketServer` class.
@ -363,21 +375,21 @@ For more information, could you see **[Example3]**?
#### Per-message Compression ####
#### Per-message Compression ####
**websocket-sharp** supports **[Per-message Compression][compression]** extension. (But, does not support with [extension parameters].)
**websocket-sharp** supports **[Per-message Compression][compression]** extension. (But it doesn't support with [extension parameters].)
If you want to enable this extension as a WebSocket client, you should do like the following.
If you enable this extension as a WebSocket client, you should do the following.
```cs
```cs
ws.Compression = CompressionMethod.DEFLATE;
ws.Compression = CompressionMethod.DEFLATE;
```
```
And then your client sends the following header in the opening handshake to a WebSocket server.
And then your WebSocket client sends the following header in the opening handshake to a WebSocket server.
```
```
Sec-WebSocket-Extensions: permessage-deflate
Sec-WebSocket-Extensions: permessage-deflate
```
```
If the server supports this extension, responds the same header. And when your client receives the header, enables this extension.
If the server supports this extension, it responds the same header. And when your client receives the header, it enables this extension.
### Secure Connection ###
### Secure Connection ###
@ -457,12 +469,7 @@ Could you access to [http://localhost:4649](http://localhost:4649) to do **WebSo
sta
12 years ago