• From: David Megginson <david@m...>
• To: "Clark C. Evans" <clark.evans@m...>
• Date: 16 Dec 1999 09:23:54 -0500

"Clark C. Evans" <clark.evans@m...> writes:

> SAX is a stream interface, but unfortunately,
> an event/listener pattern was not used.

SAX doesn't use the Java version of the event/listener stuff because
an XML document will generate several thousand events in a second or
two, and you'd really, really start to notice the overhead (unlike a
GUI, where you'll see at most a couple of dozen events in a second,
and usually much less).  It's very easy to implement the Java event
stuff on top of SAX if you want it, but there wasn't a good reason to
impose it on everyone.


All the best,


David

-- 
David Megginson                 david@m...
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • SAX and DOM
    • From: "Clark C. Evans" <clark.evans@m...>

• Prev by Date: Re: SAX2: Namespace Processing and NSUtils helper class
• Next by Date: re: Inheritance in Xml, (Xpointer??)
• Previous by thread: SAX and DOM
• Next by thread: Re: Xpath and DOM
• Index(es):
  • Date
  • Thread