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.
In generally I have absolutely no problems using URLConnection. The code I've written works marvelously in the emulator, and I have other non-Android projects that use URLConnection, so I am not exactly sure what's wrong. On Nov 24, 2:10 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > joshv wrote: > > That's why I am asking if I am doing something wrong or > > if there is some other API I should try. I can try out the Apache > > HTTPComponents, but I am assuming they just wrap the lower level java > > network APIs. I am not sure what benefit I would get. > > You want to find out if there is "some other API [you] should try", but > then you don't want to try it because you are "not sure what benefit > [you] would get"? > > I can tell you that URLConnection gave me tons of grief on Java SE and I > abandoned it ages ago in favor HTTPComponents (originally called > HTTPClient). I can tell you that I have not experienced any of the > problems you describe when using HTTPComponents on Android, though I > have mostly been using WiFi due to weak T-Mo signal strength and no 3G > in my work area. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > > Android Training on the Ranch! -- Mar 16-20, > 2009http://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 android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
