Re: [hybi] Websocket: two protocols into one, and Internet rules broken

[Anthony Catel <[e-mail]>]

Le 16/06/2011 16:28, Iñaki Baz Castillo a écrit :
> 2011/6/16 Anthony Catel<[e-mail]>:
>> I mean, it the browser can open a "raw" TCP connection and implement any
>> kind of protocol.
>> This must lead to a prompt "Do you allow your browser to open a connection
>> to xxxx:xxx?" which I think it's not suitable for user experience.
> I never said that a web browser should allow opening any kind of
> communication with a remote server :)
>
> I just said that, if it's standarized, why not to allow a web browser
> to directly speak other protocols as SIP or XMPP? I don't mean raw
> speaking such protocol from JavaScript or whatever, that should be not
> allowed as per security reasons. I mean that web browsers could
> implement a SIP and/or XMPP client and provide an API (i.e. for
> JavaScript) to use it (the very same as WebSocket proposes). Security
> would be built-in within the browser implementation.
>
> PS: I don't want web browsers implementing SIP or XMPP, it was just an
> example ;)
>

Nobody said that one day a vendor isn't going to implement a wide 
deployed protocol.
But for now, I think that WebSocket is a good choice to stop the cancer 
of "long polling"
and other ugly hacks (which is what I do).

Also, WebSocket is more or less a generic protocol where you can 
encapsulate other protocol
without having to deal boring things like Origin security, 
proxy/firewall traversal, etc...