6 ms·
Websockets have been in Chrome and in use for 6 months+. http://news.ycombinator.com/item?id=989680 http://news.ycombinator.com/item?id=989680 We have thousan
by axod 16y ago
Websockets have been in Chrome and in use for 6 months+.
http://news.ycombinator.com/item?id=989680 http://news.ycombinator.com/item?id=989680
We have thousands of users using WebSocket every day. So this is kind of a pain in the neck.
- mike-cardwell 16y agoThis is what you get when you use an unfinished protocol which everybody knows is subject to change. Guess what, it might change again... They're still researching what is the best way to do this. You should be happy they're making improvements to the protocol you're using. If they say, "This is the finished product and there will be no further incompatible changes," and then make a change which breaks your app. Then you have a right to complain.
- axod 16y agoI'm looking through the spec now. There don't seem to be any improvements. Just incompatible changes made in bizarre ways. I'll post a summary of the changes tomorrow. These sort of things often seem like they're massively over engineered. You could figure out the best way to do websockets in an afternoon without too much fuss. Nothing is ever 'finished'. It's just a pain to break backward compatibility that's all.
- carussell 16y agoThese sort of things often seem like they're massively over engineered. Until you're the edge case who gets pissed off because they didn't make it flexible enough, or the boilerplate is arcane and doesn't really make sense with much of the normal use.