Re: generating attributes and content for an element

Yeah, I haven't used the pull parser myself. The memory issue though is
generally an XSLT issue. You can't process a lot of XSLT template matches or
many XPath expressions in a stream oriented manner, so essentially the whole
input DOM has to be in memory. If its a large document, then you can be
talking really serious amounts of RAM. Now maybe libxslt is smart enough to
understand what it may need to hold onto and optimize, but even one
match='//...' and you're pretty much sunk there!



On Mon, Nov 24, 2008 at 9:49 AM, Michael Kröll <[email protected]>wrote:

> Tod Harter wrote:
> > sense it is pretty much exactly what you want. The caveats are that if
> > you have VERY large documents the memory requirements can be high, and
> > if your input is not XML then you may have to jump through a few hoops
> > to get it into a libxml document object (but there are good ways to do
> > this) and the final caveat being it can be a bit annoying to output text
>
> If the VERY large documents get too large for XSLT: Petr Pajas extended
> support for libxml's pull-parser interface (xmlreader) to XML::LibXML
> with one of the latest releases. Very helpful for those...
>
> http://ufal.mff.cuni.cz/~pajas/xml_libxml.pdf<http://ufal.mff.cuni.cz/%7Epajas/xml_libxml.pdf>
>
> Regards,
> Michael
>
> --
> 063A F25E B064 A98F A479  1690 78CD D023 5E2A 6688
> http://zis.uibk.ac.at/.m/uibk.ac.at_pgp_pubkey.asc
>



-- 
The Wise adapts himself to the world. The Fool adapts the world to himself.
Therefore, all progress depends on the Fool.

_______________________________________________
Perl-XML mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs