flashwave
5a7756894b
Reintroduces separate contexts for users, channels, connections (now split into sessions and connections) and user-channel associations. It builds which is as much assurance as I can give about the stability of this commit, but its also the bare minimum of what i like to commit sooooo A lot of things still need to be broadcast through events throughout the application in order to keep states consistent but we'll cross that bridge when we get to it. I really need to stop using that phrase thingy, I'm overusing it.
106 lines
4.6 KiB
C#
106 lines
4.6 KiB
C#
namespace SharpChat;
|
|
|
|
/// <summary>
|
|
/// WebSocket Close Code Number Registry
|
|
/// https://www.iana.org/assignments/websocket/websocket.xhtml#close-code-number
|
|
/// </summary>
|
|
public enum WebSocketCloseCode : int {
|
|
/// <summary>
|
|
/// 1000 indicates a normal closure, meaning that the purpose for which the connection was established has been fulfilled.
|
|
/// </summary>
|
|
NormalClosure = 1000,
|
|
|
|
/// <summary>
|
|
/// 1001 indicates that an endpoint is "going away", such as a server going down or a browser having navigated away from a page.
|
|
/// </summary>
|
|
GoingAway = 1001,
|
|
|
|
/// <summary>
|
|
/// 1002 indicates that an endpoint is terminating the connection due to a protocol error.
|
|
/// </summary>
|
|
ProtocolError = 1002,
|
|
|
|
/// <summary>
|
|
/// 1003 indicates that an endpoint is terminating the connection because it has received a type of data it cannot accept (e.g., an endpoint that understands only text data MAY send this if it receives a binary message).
|
|
/// </summary>
|
|
UnsupportedData = 1003,
|
|
|
|
/// <summary>
|
|
/// 1005 is a reserved value and MUST NOT be set as a status code in a Close control frame by an endpoint.
|
|
/// It is designated for use in applications expecting a status code to indicate that no status code was actually present.
|
|
/// </summary>
|
|
NoStatusReceived = 1005,
|
|
|
|
/// <summary>
|
|
/// 1006 is a reserved value and MUST NOT be set as a status code in a Close control frame by an endpoint.
|
|
/// It is designated for use in applications expecting a status code to indicate that the connection was closed abnormally, e.g., without sending or receiving a Close control frame.
|
|
/// </summary>
|
|
AbnormalClosure = 1006,
|
|
|
|
/// <summary>
|
|
/// 1007 indicates that an endpoint is terminating the connection because it has received data within a message that was not consistent with the type of the message (e.g., non-UTF-8 [RFC3629] data within a text message).
|
|
/// </summary>
|
|
InvalidFramePayloadData = 1007,
|
|
|
|
/// <summary>
|
|
/// 1008 indicates that an endpoint is terminating the connection because it has received a message that violates its policy.
|
|
/// This is a generic status code that can be returned when there is no other more suitable status code (e.g., 1003 or 1009) or if there is a need to hide specific details about the policy.
|
|
/// </summary>
|
|
PolicyViolation = 1008,
|
|
|
|
/// <summary>
|
|
/// 1009 indicates that an endpoint is terminating the connection because it has received a message that is too big for it to process.
|
|
/// </summary>
|
|
MessageTooBig = 1009,
|
|
|
|
/// <summary>
|
|
/// 1010 indicates that an endpoint (client) is terminating the connection because it has expected the server to negotiate one or more extension, but the server didn't return them in the response message of the WebSocket handshake.
|
|
/// The list of extensions that are needed SHOULD appear in the /reason/ part of the Close frame.
|
|
/// Note that this status code is not used by the server, because it can fail the WebSocket handshake instead.
|
|
/// </summary>
|
|
MandatoryExtension = 1010,
|
|
|
|
/// <summary>
|
|
/// 1011 indicates that a server is terminating the connection because it encountered an unexpected condition that prevented it from fulfilling the request.
|
|
/// </summary>
|
|
InternalError = 1011,
|
|
|
|
/// <summary>
|
|
/// 1012 indicates that the service is restarted.
|
|
/// A client may reconnect, and if it choses to do, should reconnect using a randomized delay of 5 to 30 seconds.
|
|
/// </summary>
|
|
ServiceRestart = 1012,
|
|
|
|
/// <summary>
|
|
/// 1013 indicates that the service is experiencing overload.
|
|
/// A client should only connect to a different IP (when there are multiple for the target) or reconnect to the same IP upon user action.
|
|
/// </summary>
|
|
TryAgainLater = 1013,
|
|
|
|
/// <summary>
|
|
/// The server was acting as a gateway or proxy and received an invalid response from the upstream server.
|
|
/// This is similar to 502 HTTP Status Code.
|
|
/// </summary>
|
|
GatewayTimeout = 1014,
|
|
|
|
/// <summary>
|
|
/// 1015 is a reserved value and MUST NOT be set as a status code in a Close control frame by an endpoint.
|
|
/// It is designated for use in applications expecting a status code to indicate that the connection was closed due to a failure to perform a TLS handshake (e.g., the server certificate can't be verified).
|
|
/// </summary>
|
|
TlsHandshake = 1015,
|
|
|
|
/// <summary>
|
|
/// Unauthorized (HTTP 401)
|
|
/// </summary>
|
|
Unauthorized = 3000,
|
|
|
|
/// <summary>
|
|
/// Forbidden (HTTP 403)
|
|
/// </summary>
|
|
Forbidden = 3003,
|
|
|
|
/// <summary>
|
|
/// Timeout (HTTP 408)
|
|
/// </summary>
|
|
Timeout = 3008,
|
|
}
|