They're being fixed. It'll probably take a while. Best bet right now is to develop against http://socket.io/ http://socket.io/. I'm pretty sure that will be upd

They're being fixed. It'll probably take a while. Best bet right now is to develop against http://socket.io/ http://socket.io/. I'm pretty sure that will be updated when a secure websockets protocol is implemented. Also, for now, you can use a fallback of flash sockets which in my testing perform nearly as well (all the other fallbacks perform pretty poorly if you care about latency at all)