Re: Proposal: add websocket close codes for server not found and/or too many websockets open

2012-06-01 Thread Jason Duell
On 05/28/2012 04:03 AM, Takeshi Yoshino wrote: The protocol spec has defined 1015, but I think we should not pass through it to the WebSocket API. http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0437.html I think 1006 is the right code for all of WebSocket handshake failure, TLS

Re: Proposal: add websocket close codes for server not found and/or too many websockets open

2012-05-23 Thread Jason Duell
, because WS's are long-lived and there's thus no obvious wait time bounds). Thanks for the feedback. Jason Duell Mozilla

Proposal: add websocket close codes for server not found and/or too many websockets open

2012-05-18 Thread Jason Duell
sockets will have some limit on the number of websockets it allows to be open at once (to prevent DoS attacks if nothing else). I'm not sure of what the right close code for this is. Ideas? Perhaps we could also use a dedicated code for this case too. Jason Duell Mozilla

Proposal: add websocket close codes for server not found and/or too many websockets open

2012-05-18 Thread Jason Duell
sockets will have some limit on the number of websockets it allows to be open at once (to prevent DoS attacks if nothing else). I'm not sure of what the right close code for this is. Ideas? Perhaps we could also use a dedicated code for this case too. Jason Duell Mozilla