On Fri, 2004-12-31 at 16:37 -0800, Bob Foster wrote:
> Right. In order to process a SAX stream in parallel you have to copy the
> data in the stream, you can't just "forward" the events. You also have
> to instantiate a context for each event, including at least the
> namespaces in scope, the Location info. I didn't mean to imply this
> would be excessively expensive, just not as lightweight as serially
> processed SAX.
Maybe this is where my perspective, so surprising to so many here, comes
from. In Python SAX, all event objects are dissociated from the driver.
I must say I think it somewhat vindicates the Python approach that it so
easily extends the framework to advanced implementation strategies.
I had forgotten this about the original SAX, and I must say it makes for
a lot more of an "assembler-level" view than SAX as I'm used to using
it.
--
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Use CSS to display XML - http://www.ibm.com/developerworks/edu/x-dw-x-xmlcss-i.html
Full XML Indexes with Gnosis - http://www.xml.com/pub/a/2004/12/08/py-xml.html
Be humble, not imperial (in design) - http://www.adtmag.com/article.asp?id=10286
UBL 1.0 - http://www-106.ibm.com/developerworks/xml/library/x-think28.html
Use Universal Feed Parser to tame RSS - http://www.ibm.com/developerworks/xml/library/x-tipufp.html
Default and error handling in XSLT lookup tables - http://www.ibm.com/developerworks/xml/library/x-tiplook.html
A survey of XML standards - http://www-106.ibm.com/developerworks/xml/library/x-stand4/
The State of Python-XML in 2004 - http://www.xml.com/pub/a/2004/10/13/py-xml.html
