Gah, let's hope Microsoft gets some vision for IE too. (or ditch it like Bing ditched Live)
1. They have to (meaning their current methods no longer do anything or the software or hardware no longer works).
2. Someone more savvy does it for them and teaches them the new software. Usually this happens after #1.
Unfortunately, I don't know if there's much we can do about this kind of user. We shouldn't (and won't) have to hold ourselves back because they refuse to upgrade.
We need to remember that our job is to make the computer better for other people - not just ourselves. I'm amazed at the rate of development I've seen in browser technology, but let's not forget the millions of people that just want to get online and send an email. If we rush to upgrade everyone to "better" technology - we might end up ruining their experience.
Also, you can just enable it when it's available, and fallback to comet etc when it's not.
I recently did a bit of consulting work for a guy who has a large number of domains receiving primarily organic search traffic. Around 20% of the people hitting those (several million a month) are still using IE6.
This is the best of both worlds; Flash works for IE users, and Web Sockets will hopefully be available soon in plenty of non-Flash browsers (like the iPhone).
If Websocket has something like crossdomain.xml does that mean we can build p2p applications on that?
ws.onclose = function() { // websocket is closed. };
someone reformatted the code without checking...I'm sure Google has developed some serious technology to address this while building Wave. Wondering if some of it come to Google AppEngine anytime soon?
how was this implemented before local storage? every current version of browsers supports it apart from chrome (and opera?)
saying that it is pretty awesome, web sockets have been a long time coming