Re: [hybi] Additional WebSocket Close Error Codes

On 05/24/2012 08:52 AM, Alexey Melnikov wrote:
> On 21/05/2012 11:45, Greg Wilkins wrote:
>>
>> They both look reasonable.
>
> Ok, I will register these, but I will call the second one "Try Again 
> Later" instead of "Service Overload". "Try Again Later" is used by 
> other protocols and the meaning is more generic.
>

I never got much of an answer about adding a new code for "client has 
too many websockets open", but let me ask it again.   We could 
conceivably have your proposed 1013 code  ("try again later") cover this 
case.   But one downside of this is that it doesn't distinguish between 
the case where the application could open a connection to another server 
(a particular server is overloaded), and the case where no websockets 
are going to work unless/until some existing ones go away (Client 
websocket limit reached).  So I suggest we want different codes for these.

This could look like

    1013    "Server busy"
    1014     "Too many websockets open in client"

assuming 1014 isn't taken yet--where's the list of proposed codes?

Thoughts?

Jason Duell
Mozilla

>> On 17 May 2012 11:05, Arman Djusupov <arman@noemax.com 
>> <mailto:arman@noemax.com>> wrote:
>>
>>     Yes. These status codes do make sense and it is preferable to
>>     have them
>>     standardized.
>>
>>     With best regards,
>>     Arman
>>
>>     -----Original Message-----
>>     From: hybi-bounces@ietf.org <mailto:hybi-bounces@ietf.org>
>>     [mailto:hybi-bounces@ietf.org <mailto:hybi-bounces@ietf.org>] On
>>     Behalf Of
>>     Alexey Melnikov
>>     Sent: Wednesday, May 16, 2012 12:42 PM
>>     To: Hybi
>>     Subject: [hybi] Additional WebSocket Close Error Codes
>>
>>     Hi WG,
>>     I am sorry I didn't followup on this when the following 2 codes were
>>     suggested (See
>>     <http://www.ietf.org/mail-archive/web/hybi/current/msg09284.html>):
>>
>>     1012/Service Restart
>>     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 -
>>     30s.
>>
>>     Use case:
>>     restart a service with 100k clients connected
>>     clients present an informative user notification ("service
>>     restarting ..
>>     reconnecting in N secs)
>>     clients should not reconnect all at exactly the same time .. thus the
>>     randomized delay
>>
>>
>>     1013/Service Overload
>>     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.
>>
>>     Use case:
>>     clients present an informative user notification ("service
>>     overload ..
>>     try later or try different IP)
>>
>>     -----
>>
>>     Do people use these and is there still some interest in
>>     registering them?
>>
>>     Best Regards,
>>     Alexey
>>
>>     _______________________________________________
>>     hybi mailing list
>>     hybi@ietf.org <mailto:hybi@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/hybi
>>
>>     _______________________________________________
>>     hybi mailing list
>>     hybi@ietf.org <mailto:hybi@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/hybi
>>
>>
>
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi