Re: [Fwd: Re: Xml-commons]

Iain Shigeoka <[email protected]>
Newsgroups gmane.text.xml.xmlpull.devel
Message-ID <B97FD2C1.9C59%[email protected]>
On 8/14/02 7:39 AM, "Aleksander Slominski" <[email protected]>
wrote:

> let us know if you have any comments about API and we surely
> will look on what we can do to improve pull parsing
> (but keep in mind that we wanted to make it easy to implement
> efficiently xml pull parsing and have more sophisticated features
> layered on top of XmlPull API like lightweight DOM,
> incremental XPATH etc).

Thanks Alek,

I really like the pull parser interface so far.  I have no real input yet
other than it seems to work well.  I would very much like to see lightweight
DOM and XPATH support as both would be invaluable for my code.  I have a
hacked up DOM like object that I had to put together to store the document
and sub-document data.   However, I'd love to ditch it in favor of an
actual, engineered DOM tree.  :)

I also don't know if this is a common thing but I personally need XPP to be
able to handle a lot of parallel parsed documents.  Basically I'm reading in
streaming XML from sockets for the Jabber protocol (www.jabber.org) and
there is the potential for thousands of persistent connections each with a
streaming XML document being parsed.  Things like document tag names and
some attributes will be repeated many times both in each stream, and between
streams.  So if there could be an option or a hook so that we can pool
strings from the documents it would help immensely both in string object
creation/collection and memory footprint.

Best wishes

-iain
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.