@jcoglan's should-be-FAQ for users of Faye wondering about WebSockets...

gistfile1.txt

1. Heroku doesn't support WebSocket
2. nginx doesn't (until this week) support WebSocket
3. Your customer's firewall doesn't support WebSocket
4. Internet Explorer
5. None of this matters, it will switch to other network transports for you
6. Web software has things like TCP timeouts. Don't make connectivity assumptions
7. That doesn't matter either because the client handles reconnection for you
8. EventMachine
9. Rack and/or Rails and/or blocking I/O
10. Memory leaks, which are actually my fault

(The general uselessness of Opera was implicit in all those, I hope that was clear)

Seriously though, what's really frustrating are questions that indicate we haven't explained how any of this socket stuff works at all.

e.g. People constantly assuming Faye is just a WebSocket library, or asking if they can use it to talk to Socket.IO

Not hating on users, this is just a sign we library authors aren't communicating well enough :/