Hello, O List,
I've been working on updating an SGML transformation module of mine to use
the newer XML tools and interfaces, but the SAX mechanism can't support my
module unless I split it into threads/processes (or otherwise do horrible
things to it). PerlSAX seems to force event handlers to return before the
parsing continues, and I haven't found a way around it. This "call handler
and wait" style may follow naturally from the OO/java way of doing things,
but it really gets in the way of some other setups. So I'd like to ask if
the PerlSAX interface might be altered to also support a "request next
event" style (same event names, properties, etc.)?
Personally, I think the strongest argument in favor of request-event style
is that it's trivial to do call-handlers with request-event, but not the
other way around. Perl ought to support more that just one way--but
especially the "easy" way ;)
Thanks for considering,
Robert Braddock
[PS I'm sorry if this was discussed already--I did try to browse the
archive. The interface is outright painful, especially with lynx. Is the
list archived anywhere besides activestate.com?]
---
You are currently subscribed to perl-xml as: [[email protected]]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
