I found that it works well for us... I didn't profile the memory consumption but I also didn't experience any noticeable system or app slow downs, so I didn't feel it was necessary. At the end of the day, it's pretty clear that you're trading in some performance for stability and ease of use here. I found that it was well worth it, but that probably depends on the app you're developing.
The point is: If you need a full fledged XML parser that does things such as text node merging an entity ref resolution (at least the former you will almost certainly want to have for ANY XML document), you don't have much of a choice: you either use existing, well proven solutions (such as dom4j), or you use the bare XML tools Android gives you and write everything else yourself on top of that. If the latter approach will arrive at a result which performs better than say, dom4j, AND does everything you actually need, then that's cool. I didn't see myself re- inventing the wheel though. On May 19, 5:14 pm, Zero <zeroo...@googlemail.com> wrote: > as much as i love dom4j (and i do!), how is performance on the > hardware ? > dom4j tends to suck in a lot of memory, so..uh..dunno. > > On May 19, 2:17 pm, Matthias <m.kaepp...@googlemail.com> wrote: > > > Hey guys, > > > in case you're looking for easy and powerful XML parsing on Android, > > you may be interested in > > this:http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpa... > > > Cheers, > > Matthias > > --~--~---------~--~----~------------~-------~--~----~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
