c#winfrom实现websocket连接

<?xml version="1.0"?> <doc> <assembly> <name>websocket-sharp</name> </assembly> <members> <member name="T:WebSocketSharp.ByteOrder"> <summary> Specifies the byte order. </summary> </member> <member name="F:WebSocketSharp.ByteOrder.Little"> <summary> Specifies Little-endian. </summary> </member> <member name="F:WebSocketSharp.ByteOrder.Big"> <summary> Specifies Big-endian. </summary> </member> <member name="T:WebSocketSharp.CloseEventArgs"> <summary> Represents the event data for the <see cref="E:WebSocketSharp.WebSocket.OnClose"/> event. </summary> <remarks> <para> That event occurs when the WebSocket connection has been closed. </para> <para> If you would like to get the reason for the close, you should access the <see cref="P:WebSocketSharp.CloseEventArgs.Code"/> or <see cref="P:WebSocketSharp.CloseEventArgs.Reason"/> property. </para> </remarks> </member> <member name="P:WebSocketSharp.CloseEventArgs.Code"> <summary> Gets the status code for the close. </summary> <value> A <see cref="T:System.UInt16"/> that represents the status code for the close if any. </value> </member> <member name="P:WebSocketSharp.CloseEventArgs.Reason"> <summary> Gets the reason for the close. </summary> <value> A <see cref="T:System.String"/> that represents the reason for the close if any. </value> </member> <member name="P:WebSocketSharp.CloseEventArgs.WasClean"> <summary> Gets a value indicating whether the connection has been closed cleanly. </summary> <value> <c>true</c> if the connection has been closed cleanly; otherwise, <c>false</c>. </value> </member> <member name="T:WebSocketSharp.CloseStatusCode"> <summary> Indicates the status code for the WebSocket connection close. </summary> <remarks> <para> The values of this enumeration are defined in <see href="http://tools.ietf.org/html/rfc6455#section-7.4"> Section 7.4</see> of RFC 6455. </para> <para> "Reserved value" cannot be sent as a status code in closing handshake by an endpoint. </para> </remarks> </member> <member name="F:WebSocketSharp.CloseStatusCode.Normal"> <summary> Equivalent to close status 1000. Indicates normal close. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.Away"> <summary> Equivalent to close status 1001. Indicates that an endpoint is going away. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.ProtocolError"> <summary> Equivalent to close status 1002. Indicates that an endpoint is terminating the connection due to a protocol error. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.UnsupportedData"> <summary> Equivalent to close status 1003. Indicates that an endpoint is terminating the connection because it has received a type of data that it cannot accept. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.Undefined"> <summary> Equivalent to close status 1004. Still undefined. A Reserved value. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.NoStatus"> <summary> Equivalent to close status 1005. Indicates that no status code was actually present. A Reserved value. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.Abnormal"> <summary> Equivalent to close status 1006. Indicates that the connection was closed abnormally. A Reserved value. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.InvalidData"> <summary> Equivalent to close status 1007. Indicates that an endpoint is terminating the connection because it has received a message that contains data that is not consistent with the type of the message. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.PolicyViolation"> <summary> Equivalent to close status 1008. Indicates that an endpoint is terminating the connection because it has received a message that violates its policy. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.TooBig"> <summary> Equivalent to close status 1009. Indicates that an endpoint is terminating the connection because it has received a message that is too big to process. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.MandatoryExtension"> <summary> Equivalent to close status 1010. Indicates that a client is terminating the connection because it has expected the server to negotiate one or more extension, but the server did not return them in the handshake response. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.ServerError"> <summary> Equivalent to close status 1011. Indicates that a server is terminating the connection because it has encountered an unexpected condition that prevented it from fulfilling the request. </summary> </member> <member name="F:WebSocketSharp.CloseStatusCode.TlsHandshakeFailure"> <summary> Equivalent to close status 1015. Indicates that the connection was closed due to a failure to perform a TLS handshake. A Reserved value. </summary> </member> <member name="T:WebSocketSharp.CompressionMethod"> <summary> Specifies the method for compression. </summary> <remarks> The methods are defined in <see href="https://tools.ietf.org/html/rfc7692"> Compression Extensions for WebSocket</see>. </remarks> </member> <member name="F:WebSocketSharp.CompressionMethod.None"> <summary> Specifies no compression. </summary> </member> <member name="F:WebSocketSharp.CompressionMethod.Deflate"> <summary> Specifies DEFLATE. </summary> </member> <member name="T:WebSocketSharp.ErrorEventArgs"> <summary> Represents the event data for the <see cref="E:WebSocketSharp.WebSocket.OnError"/> event. </summary> <remarks> <para> That event occurs when the <see cref="T:WebSocketSharp.WebSocket"/> gets an error. </para> <para> If you would like to get the error message, you should access the <see cref="P:WebSocketSharp.ErrorE