Re:Tether Launches HTML5-Based iPhone Tethering Solution
by saurik on Friday March 09, 2012 @11:18PM
(#3687025)
My experience is the exact opposite: all networks I've used in the US (Sprint, Verizon, AT&T, and T-Mobile; in essence, all of the major ones) and the few I've used in the UK (while roaming) have all had sufficiently few outgoing ports blocked that I've never run into one (and I use my iPhone as if it were a computer ;P). That said, WebSockets is just an upgrade extension to HTTP, so it is going to go over 80/443 anyway.
Re:Tether Launches HTML5-Based iPhone Tethering Solution
by jcitme on Sunday March 11, 2012 @04:24PM
(#3691189)
Same experience here. I use SSH over a wide variety of ports, and never had it blocked by 3G before...
Re:Tether Launches HTML5-Based iPhone Tethering Solution
by shankinson on Friday March 09, 2012 @07:12PM
(#3686577)
Yes they do. We've tested them on iPhones, BlackBerry browser, and the Aurora browser on Android.
Re:Tether Launches HTML5-Based iPhone Tethering Solution
by kenrikm on Friday March 09, 2012 @08:28PM
(#3686739)
I was able to get the original before it was pulled from the App Store. it worked well, glad to see they found a work around. I expect some type of backlash from AT&T/Verizon/Sprint However, I hope they make enough to afford the lawyers.
Re:Tether Launches HTML5-Based iPhone Tethering Solution
by mikeash on Friday March 09, 2012 @08:40PM
(#3686767)
Non-web stuff works fine on the mobile networks I've tried it on. I occasionally ssh from my phone directly to my home computer or server, and I've never had a problem with it. Skype works fine over cell data, as do various instant messaging clients.
Even if that weren't true, websockets was designed to look a whole lot like HTTP precisely so that it could work with existing proxies and firewalls.
I'm not really aware of that stuff, but I'm a bit curious. Do websockets really work over mobile networks (which are, at least in my experience, transparent proxied, and where anything outside of HTTP-on-port-80/HTTPS-on-port-443 is blacklisted into oblivion) ?