3 ms·
One of the very real issues with WebSockets is that they don't work often over mobile networks, with invisible proxying, etc. Unless you go with something like
by rizwan 14y ago
One of the very real issues with WebSockets is that they don't work often over mobile networks, with invisible proxying, etc.
Unless you go with something like Socket.IO, WebSockets alone would never be a viable solution.
- leggetter 14y agoFrom my experience, working at Pusher and dealing with support for the past year, WebSockets do work over a mobile 3G connection when you use an SSL (wss://) connection. I tether (laptop -> mobile -> mobile data) quite a bit whilst travelling and my mobile data provider, O2, do all sorts of annoying things with dat (stop whitespace, inject JavaScript), but my WebSocket connections work flawlessly. In the same way that a WebSocket library can fallback from a WebSocket connection to a HTTP-based connection it can also first try ws:// and then fallback to wss:// - it's what our library does. The potential problem here of course is that you need an SSL certificate. When using Pusher that's not a problem, because we've bought one, but when using your own hosted solution that might mean dishing out money that you'd rather not.
- cft 14y agoTry a port other than 80: I have my iPod tethered via Droid 3 on a Verizon 3G network, it blocks 80, but did not block 1800