On Mon, Oct 27, 2008 at 5:57 PM, Hong <[EMAIL PROTECTED]> wrote:
>
> you can use DocumentBuilder from DocumentBuilderFactory to access DOM :)
>
Yes, but parsing xml via the DOM is slow and hogs memory, and avoiding
that is the point of this thread.
--~--~-~--~~~---~--~
you can use DocumentBuilder from DocumentBuilderFactory to access DOM :)
--~--~-~--~~~---~--~~
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
On Mon, Oct 27, 2008 at 6:01 AM, Guillaume Perrot
<[EMAIL PROTECTED]> wrote:
>
> 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.
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
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
By it's nature DOM is memory intensive. Using the SAX parser will
allow you to possibly quickly reclaim memory but still involves quite
a bit of processing b/c these APIs were written to be quite robust.
Considering this is a mobile platform where we're encouraged to
optimize things that would no
Casey Link wrote:
> Is there a
> recommended/preferred/faster way of making POST/GET requests, and
> parsing XML in the android?
On the XML front, the XML Pull Parser (org.xmlpull.*) is supposed to be
pretty quick.
--
Mark Murphy (a Commons Guy)
http://commonsware.com
_The Busy Coder's Guide t
I believe that this issue should be addressed by the Android team
since it is of general interest. My guess is that the virtual machine
reduces speed compared to with native code with a factor of 10 or so.
The only reasonable work-around is to do a mixed implementation where
some of the parts are
8 matches
Mail list logo
