* adding server down and server recovered messages for VRFS-196

This commit is contained in:
Seth Call 2013-07-14 21:45:20 -05:00
parent 60ae5c1b35
commit 6342d5d41f
1 changed files with 24 additions and 0 deletions

View File

@ -33,9 +33,12 @@ message ClientMessage {
PEER_MESSAGE = 302;
TEST_CLIENT_MESSAGE = 303;
SERVER_BAD_STATE_RECOVERED = 900;
SERVER_GENERIC_ERROR = 1000;
SERVER_REJECTION_ERROR = 1001;
SERVER_PERMISSION_ERROR = 1002;
SERVER_BAD_STATE_ERROR = 1003;
}
// Identifies which inner message is filled in
@ -73,10 +76,14 @@ message ClientMessage {
optional PeerMessage peer_message = 302;
optional TestClientMessage test_client_message = 303;
// Server-to-Client special messages
optional ServerBadStateRecovered server_bad_state_recovered = 900;
// Server-to-Client errors
optional ServerGenericError server_generic_error = 1000;
optional ServerRejectionError server_rejection_error = 1001;
optional ServerPermissionError server_permission_error = 1002;
optional ServerBadStateError server_bad_state_error = 1003;
}
// route_to: server
@ -241,6 +248,14 @@ message SessionInvitation {
optional string invitation = 1;
}
// route_to: client
// this should follow a ServerBadStateError in the case that the
// websocket gateway recovers from whatever ailed it
message ServerBadStateRecovered {
}
// route_to: client
// this indicates unhandled error on server
// if you receive this, your connection will close after.
@ -263,3 +278,12 @@ message ServerRejectionError {
message ServerPermissionError {
optional string error_msg = 1;
}
// route_to: client
// this indicates that the server is in a bad state, but could recover later, and is unable to process the request
// your connection is not closed if this message occurs
message ServerBadStateError {
optional string error_msg = 1;
}