Re: [hybi] Yet more additional WebSocket Close Error Codes

[Julian Reschke <[e-mail]>]

On 2012-05-18 06:20, Jason Duell wrote:
> I'm wondering if there are two more close codes that would be useful,
> to indicate
>
>    1) remote server not reachable
>
>    2) client/browser has too many websockets open already (try later)
>
> Re: #1: Both Web Socket specs are a little vague IMO on how JS is
> notified when the targeted web socket server is down/nonexistent/etc.
>
> Firefox is firing an 'error' event when this happens, based AFAICT on
> the language here in the W3C spec:
>
>    "if the status code received from the server is not 101 (e.g. it is
> a redirect), the user agent must fail the websocket connection"

Well, no status code was received at all; so this doesn't seem to help :-)

> Chrome is not calling onerror for this, so we have a difference here.
> The language in the spec isn't really clear if this covers the
> connection-never-happened case.

I think it is; but I agree that the behavior for the other case should 
be specified at all.

> ...

Anyway; I think this should be raised as a WSAPI problem.

Best regards, Julian