Re: [hybi] Additional WebSocket Close Error Codes

[Jason Duell <[e-mail]>]

On 05/29/2012 04:15 AM, Alexey Melnikov wrote:
>
>> 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),
>
> I think having a new code for "try another server" would be better, as 
> it is more explicit that an immediate action can be attempted (where 
> "server overload" or "try again later" imply that an action in a 
> future can be attempted). Would such split work for you?

There may not be another server, so "try another server" isn't always 
applicable.   So my vote would go to "server overload".   But I don't 
have strong feelings about it, so long as it's differentiated from 
client websocket limit reached.

cheers,

Jason
Mozilla


>> 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"
>>