parse_chunk()

Simple question: XML::LibXML::SAX has a parse_chunk()
method.  Is  
there a similar method for XML::SAX::ExpatXS?  What I am
looking for  
is a way to basically 'pause' parsing when a specific event
is  
triggered, then start again from the pause point when
needed.  I am  
also looking into using XML::Twig, but changing over would
require  
refactoring the current XML::SAX-based code.

The reason I ask is that we (BioPerl) are parsing XML output
which  
had one result object generated per XML report (NCBI BLAST
XML).  The  
object ref is easily returned via end_document().  However
NCBI has  
recently changed their XML output so that multiple result
objects are  
now generated per XML report.  I could cache the objects and
returned  
them all at once, but these reports can potentially become
very large  
(possibly GByte), so caching all the objects isn't the best
long-term  
solution.

chris
_______________________________________________
Perl-XML mailing list
Perl-XMLlistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs

Chris Fields wrote:
> Simple question: XML::LibXML::SAX has a parse_chunk()
method.  Is  
> there a similar method for XML::SAX::ExpatXS?  


No, ExpatXS only implements Perl SAX which is a simple push
interface. But I 
will think about a possibility to pause parsing (as recent
versions of Expat 
support this feature).

Best,
Petr


What I am looking for
> is a way to basically 'pause' parsing when a specific
event is  
> triggered, then start again from the pause point when
needed.  I am  
> also looking into using XML::Twig, but changing over
would require  
> refactoring the current XML::SAX-based code.
> 
> The reason I ask is that we (BioPerl) are parsing XML
output which  
> had one result object generated per XML report (NCBI
BLAST XML).  The  
> object ref is easily returned via end_document(). 
However NCBI has  
> recently changed their XML output so that multiple
result objects are  
> now generated per XML report.  I could cache the
objects and returned  
> them all at once, but these reports can potentially
become very large  
> (possibly GByte), so caching all the objects isn't the
best long-term  
> solution.
> 
> chris
> _______________________________________________
> Perl-XML mailing list
> Perl-XMLlistserv.ActiveState.com
> To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs


-- 
Petr Cimprich
Ginger Alliance
www.gingerall.com
_______________________________________________
Perl-XML mailing list
Perl-XMLlistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs