Re: [hybi] Sec-WebSocket-Protocl

[Iñaki Baz Castillo <[e-mail]>]

2011/6/21 Takeshi Yoshino <[e-mail]>:
> As Iñaki noted, subprotocol negotiation can also be done over application
> layer. The only benefit of subprotocol field in the opening handshake is
> that we can finish subprotocol negotiation in the first round-trip time (in
> an extreme case, this can also be done by embedding subprotocol choice in
> URL string and replying by the first frame from server).

In fact, if Sec-WebSocket-Protocol header was not exist, I expect
nobody would miss it. WebSocket services will be served by providers
also providing the JavaScript code. Maybe a webpage includes a
JavaScript code to connect to a chat and other code to connect to a
like-RSS system. Webdevelopers will just enable two different WS URI
(ws://mydomain.org/chat and ws://mydomain.org/rss) and the JavaScript
client will just connect to each one. No need of negotiation.

Honestly I don't see the benefict of standarizing or negotiating
subprotocols on top of WebSocket. Or maybe what I want to say is that
I don't believe it will succeed (as web developers are anarchic by
nature and they want to know exacty *nothing* about standars,
protocols, IANA registry names and so on).

-- 
Iñaki Baz Castillo
<[e-mail]>