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

Fix a few

Browse Source
This commit is contained in:
sta 2013-12-03 14:24:06 +09:00
parent 1ed13259b5
commit bf7717dde8
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -1,7 +1,10 @@
![Logo](websocket-sharp.png) ![Logo](websocket-sharp.png)
## Welcome to websocket-sharp! ##
**websocket-sharp** supports the followings. **websocket-sharp** supports the followings.
- **[WebSocket Client](#websocket-client)** and **[Server](#websocket-server)**
- **[RFC 6455](#supported-websocket-specifications)** - **[RFC 6455](#supported-websocket-specifications)**
- **[Per-message Compression](#per-message-compression)** extension - **[Per-message Compression](#per-message-compression)** extension
- **[Secure Connection](#secure-connection)** - **[Secure Connection](#secure-connection)**
@ -194,7 +197,7 @@ The types of `data` are `string`, `byte []` and `System.IO.FileInfo`.
In addition, the `WebSocket.Send (stream, length)` method exists, too. In addition, the `WebSocket.Send (stream, length)` method exists, too.
These methods don't wait for the send to be complete. This means that these methods behave asynchronously. These methods don't wait for the send to be complete. It means these methods behave asynchronously.
If you do something when the send is complete, you use any of some `WebSocket.Send (data, completed)` methods. If you do something when the send is complete, you use any of some `WebSocket.Send (data, completed)` methods.
@ -206,7 +209,7 @@ Closing the WebSocket connection.
ws.Close (code, reason); ws.Close (code, reason);
``` ```
If you close the WebSocket connection explicitly, you use the `WebSocket.Close` method. If you explicitly close the WebSocket connection, you use the `WebSocket.Close` method.
The `WebSocket.Close` method is overloaded. The `WebSocket.Close` method is overloaded.