According to me, the fastest combo is to use HttpClient + SAX. SAX: encouraged by the android team, they discourage the use of XmlPullParser unless we import KXml in our source tree and use this implementation. With HttpClient, you can reuse the same socket (keepalive) to make several requests one after another, so I guess it's more efficient than UrlConnection API.
On Oct 26, 7:57 pm, Christine <[EMAIL PROTECTED]> wrote: > I use httpClient, which is built into the Android. I see no > performance problem there. I use DOM for xml parsing, for just very > small replies from a server, no performance problems there. I would > like to have an alternative for DOM, just 'cause I don't like it. > Elsewhere I use Xstream which I like a lot, haven't tried that on > android. Promise you I will though. > > Christine > > On Oct 26, 4:32 am, Casey Link <[EMAIL PROTECTED]> wrote: > > > Hello, > > > My Application is consuming some remote REST services. Currently I am > > using java.net.HttpURLConnection to make the POST/GET requests, and > > javax.xml.parsers.DocumentBuilder, org.w3c.dom to parse the XML > > results. > > > I don't have any hard numbers, but it is very slow in the emulator. > > The main bottleneck seems to be the DOM parsing routines. Is there a > > recommended/preferred/faster way of making POST/GET requests, and > > parsing XML in the android? > > > Casey Link --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
