Earlier quoted context omitted.
I'm not sure if you'd really call it 'in flux'. We've been using websocket for over a year now on Mibbit. I think around 20% of our users currently do websocket. Fair enough to wait and see though, hopefully they'll do it the same way everyone else has.
By "in flux" I was intending to vaguely refer to the problems with the protocol which has led Firefox and Opera to ship with WebSockets disabled. I'm guessing we're probably going to see some changes to it in the future. Hopefully sooner rather than later. I honestly don't know a thing about the version of the protocol that they've implemented. It looks like one that they (Microsoft) have submitted - http://tools.iet…
WCF WebSockets
11–13 of 13 posts
Re: WCF WebSockets
#12Earlier quoted context omitted.
By "in flux" I was intending to vaguely refer to the problems with the protocol which has led Firefox and Opera to ship with WebSockets disabled. I'm guessing we're probably going to see some changes to it in the future. Hopefully sooner rather than later. I honestly don't know a thing about the version of the protocol that they've implemented. It looks like one that they (Microsoft) have submitted - http://tools.iet…
Yeah - A "hoo-haw" is good. The quicker issues are brought to attention and resolved the better.
if there is a crappy silly caching proxy, an attacker can use websocket to get it to cache things it shouldn't.
I think the fact Chrome hasn't done anything about it, (especially since they can auto update and turn off support tomorrow if they wish), is telling.
Re: WCF WebSockets
#13Why don't they just implement the accepted WebSocket standard instead of their own competing API?