just figured out why web sockets (HTML5) are'nt all the rage as yet.
though the html5 browsers are all compliant and ready:
1. the server sides are lagging behind pathetically. no standard apis for websocket servlets
have a look at tomcat7 reco, websocket code
2. websocket protocol tho starts out as http and then upgrades to a full-duplex, most proxies might still not play ball, so most likely its not going to work across WANs. compliance here is inching its way. shucks.
I guess its back to long polling and COMET, yeah, at for coming year