Re: [hybi] Proposed way forward for WebSockets

[Alexey Melnikov <[e-mail]>]

Jamie Lokier wrote:
 [...]
> Critical issue:
>
> After the first deployment wave, how can client WebSocket
> implementations request features without breaking the existing
> services that *reject* and *close* connections with additional state
> in the headers?
>
> The subprotocol field (as is) cannot be used for this by a WebSocket
> API implementation because it is not allowed to change what the script
> provides.
>
> Imho a robust, extensible negotiation slot must be present early for
> this plan to work.  Assuming this is agreeable as a requirement we can
> work on making it simple, robust, and secure.
>   
+1.