333 lines
8.5 KiB
Markdown
333 lines
8.5 KiB
Markdown
# websocket-sharp #
|
|
|
|
**websocket-sharp** is a C# implementation of the WebSocket protocol client & server.
|
|
|
|
## Usage ##
|
|
|
|
### The WebSocket client ###
|
|
|
|
#### Step 1 ####
|
|
|
|
Required namespaces.
|
|
|
|
```cs
|
|
using WebSocketSharp;
|
|
using WebSocketSharp.Frame;
|
|
```
|
|
|
|
The `WebSocket` class exists in the `WebSocketSharp` namespace, the WebSocket frame resources (e.g. `WsFrame` class) exist in the `WebSocketSharp.Frame` namespace.
|
|
|
|
#### Step 2 ####
|
|
|
|
Creating a instance of the `WebSocket` class.
|
|
|
|
```cs
|
|
using (WebSocket ws = new WebSocket("ws://example.com"))
|
|
{
|
|
...
|
|
}
|
|
```
|
|
|
|
The `WebSocket` class inherits the `IDisposable` interface, so you can use the `using` statement.
|
|
|
|
#### Step 3 ####
|
|
|
|
Setting the `WebSocket` events.
|
|
|
|
##### WebSocket.OnOpen event #####
|
|
|
|
The `WebSocket.OnOpen` event occurs when the WebSocket connection has been established.
|
|
|
|
```cs
|
|
ws.OnOpen += (sender, e) =>
|
|
{
|
|
...
|
|
};
|
|
```
|
|
|
|
The `e` has come across as the `EventArgs.Empty`, so there is no operation on the `e`.
|
|
|
|
##### WebSocket.OnMessage event #####
|
|
|
|
The `WebSocket.OnMessage` event occurs when the `WebSocket` receives a data frame.
|
|
|
|
```cs
|
|
ws.OnMessage += (sender, e) =>
|
|
{
|
|
...
|
|
};
|
|
```
|
|
|
|
The `e.Type` (`WebSocketSharp.MessageEventArgs.Type`, its type is `WebSocketSharp.Frame.Opcode`) contains the **Frame type** of the data frame, so you check it out and you determine which item you should operate.
|
|
|
|
```cs
|
|
switch (e.Type)
|
|
{
|
|
case Opcode.TEXT:
|
|
...
|
|
break;
|
|
case Opcode.BINARY:
|
|
...
|
|
break;
|
|
default:
|
|
break;
|
|
}
|
|
```
|
|
|
|
If the `e.Type` is `Opcode.TEXT`, you operate the `e.Data` (`WebSocketSharp.MessageEventArgs.Data`, its type is `string`).
|
|
|
|
If the `e.Type` is `Opcode.BINARY`, you operate the `e.RawData` (`WebSocketSharp.MessageEventArgs.RawData`, its type is `byte[]`).
|
|
|
|
##### WebSocket.OnError event #####
|
|
|
|
The `WebSocket.OnError` event occurs when the `WebSocket` gets an error.
|
|
|
|
```cs
|
|
ws.OnError += (sender, e) =>
|
|
{
|
|
...
|
|
};
|
|
```
|
|
The `e.Message` (`WebSocketSharp.ErrorEventArgs.Message`, its type is `string`) contains the error message, so you operate it.
|
|
|
|
##### WebSocket.OnClose event #####
|
|
|
|
The `WebSocket.OnClose` event occurs when the `WebSocket` receives a Close frame or the `Close` method is called.
|
|
|
|
```cs
|
|
ws.OnClose += (sender, e) =>
|
|
{
|
|
...
|
|
};
|
|
```
|
|
|
|
The `e.Code` (`WebSocketSharp.CloseEventArgs.Code`, its type is `WebSocketSharp.Frame.CloseStatusCode`) contains the close status code and the `e.Reason` (`WebSocketSharp.CloseEventArgs.Reason`, its type is `string`) contains the reason why closes, so you operate them.
|
|
|
|
#### Step 4 ####
|
|
|
|
Connecting to the WebSocket server.
|
|
|
|
```cs
|
|
ws.Connect();
|
|
```
|
|
|
|
#### Step 5 ####
|
|
|
|
Sending a data.
|
|
|
|
```cs
|
|
ws.Send(data);
|
|
```
|
|
|
|
The `Send` method is overloaded.
|
|
|
|
The types of `data` are `string`, `byte[]` or `FileInfo` class.
|
|
|
|
#### Step 6 ####
|
|
|
|
Closing the WebSocket connection.
|
|
|
|
```cs
|
|
ws.Close(code, reason);
|
|
```
|
|
|
|
If you want to close the WebSocket connection explicitly, you can use the `Close` method.
|
|
|
|
The type of `code` is `WebSocketSharp.Frame.CloseStatusCode`, the type of `reason` is `string`.
|
|
|
|
The `Close` method is overloaded. (In addition, the `Close()` and `Close(code)` methods exist.)
|
|
|
|
### The WebSocket server ###
|
|
|
|
#### Step 1 ####
|
|
|
|
Required namespace.
|
|
|
|
```cs
|
|
using WebSocketSharp.Server;
|
|
```
|
|
|
|
The `WebSocketServer`, `WebSocketServer<T>` and `WebSocketService` classes exist in the `WebSocketSharp.Server` namespace.
|
|
|
|
#### Step 2 ####
|
|
|
|
Creating a class that inherits the `WebSocketService` class.
|
|
|
|
For example, if you want to provide the echo service,
|
|
|
|
```cs
|
|
using System;
|
|
using WebSocketSharp;
|
|
using WebSocketSharp.Server;
|
|
|
|
public class Echo : WebSocketService
|
|
{
|
|
protected override void onMessage(object sender, MessageEventArgs e)
|
|
{
|
|
Send(e.Data);
|
|
}
|
|
}
|
|
```
|
|
|
|
Or if you want to provide the chat service,
|
|
|
|
```cs
|
|
using System;
|
|
using WebSocketSharp;
|
|
using WebSocketSharp.Server;
|
|
|
|
public class Chat : WebSocketService
|
|
{
|
|
protected override void onMessage(object sender, MessageEventArgs e)
|
|
{
|
|
Publish(e.Data);
|
|
}
|
|
}
|
|
```
|
|
|
|
If you override the `onMessage` method, it is bound to the server side `WebSocket.OnMessage` event.
|
|
|
|
In addition, if you override the `onOpen`, `onError` and `onClose` methods, each of them is bound to the `WebSocket.OnOpen`, `WebSocket.OnError` and `WebSocket.OnClose` events.
|
|
|
|
#### Step 3 ####
|
|
|
|
Creating a instance of the `WebSocketServer<T>` class if you want the single WebSocket service server.
|
|
|
|
```cs
|
|
var wssv = new WebSocketServer<Echo>("ws://example.com:4649");
|
|
```
|
|
|
|
Creating a instance of the `WebSocketServer` class if you want the multi WebSocket service server.
|
|
|
|
```cs
|
|
var wssv = new WebSocketServer(4649);
|
|
wssv.AddService<Echo>("/Echo");
|
|
wssv.AddService<Chat>("/Chat");
|
|
```
|
|
|
|
You can add to your `WebSocketServer` any WebSocket service and a matching path to that service by using the `WebSocketServer.AddService<T>` method.
|
|
|
|
The type of `T` inherits `WebSocketService` class, so you can use a class that was created in **Step 2**.
|
|
|
|
If you create a instance of the `WebSocketServer` class without port number, `WebSocketServer` set **80** to port number automatically.
|
|
So it is necessary to run with root permission.
|
|
|
|
$ sudo mono example2.exe
|
|
|
|
#### Step 4 ####
|
|
|
|
Setting the event.
|
|
|
|
##### WebSocketServer<T>.OnError event #####
|
|
|
|
The `WebSocketServer<T>.OnError` event occurs when the `WebSocketServer<T>` gets an error.
|
|
|
|
```cs
|
|
wssv.OnError += (sender, e) =>
|
|
{
|
|
...
|
|
};
|
|
```
|
|
|
|
The `e.Message` (`WebSocketSharp.ErrorEventArgs.Message`, its type is `string`) contains the error message, so you operate it.
|
|
|
|
##### WebSocketServer.OnError event #####
|
|
|
|
Same as the `WebSocketServer<T>.OnError` event.
|
|
|
|
#### Step 5 ####
|
|
|
|
Starting the server.
|
|
|
|
```cs
|
|
wssv.Start();
|
|
```
|
|
|
|
#### Step 6 ####
|
|
|
|
Stopping the server.
|
|
|
|
```cs
|
|
wssv.Stop();
|
|
```
|
|
|
|
### The HTTP server with the WebSocket ###
|
|
|
|
I modified the `System.Net.HttpListener`, `System.Net.HttpListenerContext` and some other classes of [Mono] to create the HTTP server that can upgrade the connection to the WebSocket connection when receives a WebSocket request.
|
|
|
|
You can add to your `HttpServer` any WebSocket service and a matching path to that service by using the `HttpServer.AddService<T>` method.
|
|
|
|
```cs
|
|
var httpsv = new HttpServer(4649);
|
|
httpsv.AddService<Echo>("/");
|
|
```
|
|
|
|
For more information, please refer to the [Example3].
|
|
|
|
## Examples ##
|
|
|
|
Examples of using **websocket-sharp**.
|
|
|
|
### Example ###
|
|
|
|
[Example] connects to the [Echo server] using the WebSocket.
|
|
|
|
### Example1 ###
|
|
|
|
[Example1] connects to the [Audio Data delivery server] using the WebSocket ([Example1] is only implemented a chat feature, still unfinished).
|
|
|
|
[Example1] uses [Json.NET].
|
|
|
|
### Example2 ###
|
|
|
|
[Example2] starts the WebSocket server.
|
|
|
|
### Example3 ###
|
|
|
|
[Example3] starts the HTTP server that can upgrade the connection to the WebSocket connection.
|
|
|
|
Please access [http://localhost:4649](http://localhost:4649) to do WebSocket Echo Test with your web browser after [Example3] running.
|
|
|
|
## Supported WebSocket Protocol ##
|
|
|
|
**websocket-sharp** supports **[RFC 6455]**.
|
|
|
|
- @**[branch: hybi-00]** supports older draft-ietf-hybi-thewebsocketprotocol-00 (**[hybi-00]**).
|
|
- @**[branch: draft75]** supports even more old draft-hixie-thewebsocketprotocol-75 (**[hixie-75]**).
|
|
|
|
## Reference ##
|
|
|
|
- **[The WebSocket Protocol]**
|
|
- **[The WebSocket API]**
|
|
|
|
Thx for translating to japanese.
|
|
|
|
- **[The WebSocket Protocol 日本語訳]**
|
|
- **[The WebSocket API 日本語訳]**
|
|
|
|
## License ##
|
|
|
|
Copyright © 2010 - 2012 sta.blockhead
|
|
|
|
Licensed under the **[MIT License]**.
|
|
|
|
|
|
[Audio Data delivery server]: http://agektmr.node-ninja.com:3000/
|
|
[branch: draft75]: https://github.com/sta/websocket-sharp/tree/draft75
|
|
[branch: hybi-00]: https://github.com/sta/websocket-sharp/tree/hybi-00
|
|
[Echo server]: http://www.websocket.org/echo.html
|
|
[Example]: https://github.com/sta/websocket-sharp/tree/master/Example
|
|
[Example1]: https://github.com/sta/websocket-sharp/tree/master/Example1
|
|
[Example2]: https://github.com/sta/websocket-sharp/tree/master/Example2
|
|
[Example3]: https://github.com/sta/websocket-sharp/tree/master/Example3
|
|
[hixie-75]: http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-75
|
|
[hybi-00]: http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-00
|
|
[Json.NET]: http://james.newtonking.com/projects/json-net.aspx
|
|
[MIT License]: http://www.opensource.org/licenses/mit-license.php
|
|
[Mono]: http://www.mono-project.com/
|
|
[RFC 6455]: http://tools.ietf.org/html/rfc6455
|
|
[The WebSocket API]: http://www.w3.org/TR/websockets/
|
|
[The WebSocket API 日本語訳]: http://www.hcn.zaq.ne.jp/___/WEB/WebSocket-ja.html
|
|
[The WebSocket Protocol]: http://tools.ietf.org/html/rfc6455
|
|
[The WebSocket Protocol 日本語訳]: http://www.hcn.zaq.ne.jp/___/WEB/RFC6455-ja.html
|