• To: <xml-dev@l...>
• Subject: RE: re: XML SIG 17 September: Elliotte Rusty Harold on What's Wrong with XML APIs (and How to Fix Them)
• From: "Aaron Skonnard" <aarons@d...>
• Date: Thu, 12 Sep 2002 11:09:25 -0600
• Importance: Normal
• In-reply-to: <p04330106b9a6761f5f05@[192.168.254.4]>

Elliotte Rusty Harold wrote:

> >Sure you can, by consuming ContentHandler instead of implementing it.
> >In fact, this use of SAX is MUCH more intuitive than for reading 
> >documents.
> 
> You can do a lot of things by consuming ContentHandler, but none of
> that is a  part of SAX. SAX is a read-only API on top of which many
> applications can be built. Don't confuse the application you built
> with SAX itself.

Since when is SAX a "read-only API"? SAX is simply a suite of interface
definitions for programmatically representing XML documents. Why does it
matter what side of the interface you're on? It's still SAX.

-aaron

• References:
  • RE: re: XML SIG 17 September: Elliotte Rusty Harold on What's Wrong with XML APIs (and How to Fix Them)
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: The 11-pound solution to your XML problems
• Next by Date: Re: re: XML SIG 17 September: Elliotte Rusty Harold on What's Wrong with XML APIs (and How to Fix Them)
• Previous by thread: RE: re: XML SIG 17 September: Elliotte Rusty Harold on What's Wrong with XML APIs (and How to Fix Them)
• Next by thread: Re: re: XML SIG 17 September: Elliotte Rusty Harold on What's Wrong with XML APIs (and How to Fix Them)
• Index(es):
  • Date
  • Thread