>From the phone, connections will almost certainly be proxied by T-mobile. Perhaps it's the interaction between your server and the proxies that is at the root of your problem? Tom.
2008/11/24 joshv <[EMAIL PROTECTED]> > > It's identical code - identical URL, no SSL, using a domain name. In > the emulator I very rarely get a socket timeout - but that's because > I've set a pretty aggressive 5 second timeout - which periodically the > target website (or our intervening network path) fails to meet - this > is to be expected, but other than that it never errors out in the > emulator. If it worked this well on the actually phone I'd be > perfectly happy. > > -josh > > On Nov 24, 2:53 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > > joshv wrote: > > > I am assuming that HTTPComponents just wraps the underlying java > > > networking APIs - but perhaps I am wrong and they wrote an HTTP client > > > all the way down to the socket level. Regardless, it can't hurt to > > > try. > > > > I suspect it's written to Java sockets. > > > > > The code I've written works marvelously in the emulator > > > > Now *that's* odd. > > > > Is there anything unusual about the URL you are trying to connect to: > > SSL? Oddball port? IP address instead of domain name? The server you're > > trying to hit is on the same PC as the emulator you were running? > > > > -- > > Mark Murphy (a Commons Guy)http://commonsware.com > > > > Android Training on the Ranch! -- Mar 16-20, 2009 > http://www.bignerdranch.com/schedule.shtml > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
