Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Re^3: Incremental XML parsing

by Corion (Pope)
on Feb 04, 2012 at 16:53 UTC ( #951824=note: print w/replies, xml ) Need Help??

in reply to Re^2: Incremental XML parsing
in thread Incremental XML parsing

Thatg warning is from the documentation of "keep_encoding". I don't understand how it applies to the problem of parsing a file withohut creating the complete DOM in memory. Can you please explain how it applies?

Replies are listed 'Best First'.
Re^4: Incremental XML parsing
by Anonymous Monk on Feb 04, 2012 at 17:19 UTC
    Because it explicitly says that the non-blocking parser should not be used with XML::Twig and is untested. Yes, the author chose to include the only mention of the non-blocking parser in the documentation for an unrelated option, but the docs in general are quite confusing. As it stands, XML::LibXML::Reader has similar functionality to XML::Twig, but is much, much faster. But neither appear to be able to parse XML incrementally. Note this means not only to not produce the entire DOM at once, but also to be able to consume the input document in pieces, such as feeding data as it arrives over the wire.
      In the OP, I see only a requirement to parse large documents, in which case Twig (or XML::Rules) would likely be fine.
        OP here. I do consider incremental parsing to include incremental feeding of data to the parser. That was why I mentioned XML::SAX::Expat::Incremental.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://951824]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (7)
As of 2021-11-30 22:30 GMT
Find Nodes?
    Voting Booth?

    No recent polls found