Re: [hybi] Additional WebSocket Close Error Codes

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] 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
https://www.ietf.org/mailman/listinfo/hybi