Well, a stop now i'm done message would be good, but better still the
boolean return would mean just child events of this element are skipped. I
would still get events for siblings/future uncles (etc) of this element.
Often times you have a structure like (well heavens, not this per se, but
you get the idea)
<root>
<a> -- arbitrarily deep content </a>
<b> -- arbitrarily deep content </b>
<c> -- arbitrarily deep content</c>
....
....
<z> -- arbitrarily deep content </z>
</root>
and you only want to fully parse <a> <p> and <q>
the other you just want to skip completely.
--dave
----- Original Message -----
From: "Joseph Kesselman" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, March 29, 2006 11:30 AM
Subject: [OT] A Sax response to Stax
On Tuesday, 03/28/2006 at 09:02 EST, "Dave Brosius" <[EMAIL PROTECTED]>
wrote:
I've always wondered why ContentHandler's startElement didn't return a
boolean as to whether child content event notification was desired. Seems
like that would improve sax performance significantly for many
applications.
... or a "you can stop parsing now; no more events will be needed"
mechanism other then throwing an exception. (Heck, even an exception
reserved for the purpose would do the job.)
Is SAX still it's own organization? Or has its maintainance been taken
over
by someone else by now (Apache, W3C, Oasis,....?)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
