• From: David Megginson <david@m...>
• To: XML Dev <xml-dev@i...>
• Date: Tue, 9 Mar 1999 14:51:08 -0500 (EST)

Glenn Vanderburg writes:

 > Second: if an application needs to implement certain features by 
 > pushing filters from the bottom, it can encapsulate the entire process
 > on its own, using a composite, and the process never needs to be 
 > exposed through the ModSAX API.

This is actually a good point.  Since the SAX driver is usually a
separate class rather than the parser itself, it would not be
difficult for it to encapsulate any needed filters.


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 (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe 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 RFD: ModSAX Predefined Features
    • From: David Megginson <david@m...>
  • Re: SAX RFD: ModSAX Predefined Features
    • From: John Cowan <cowan@l...>
  • Re: SAX RFD: ModSAX Predefined Features
    • From: Glenn Vanderburg <glv@v...>

• Prev by Date: Re: SAX: ModSAX addition, general property query
• Next by Date: Re: SAX: ModSAX addition, general property query
• Previous by thread: Re: SAX RFD: ModSAX Predefined Features
• Next by thread: Re: SAX RFD: ModSAX Predefined Features
• Index(es):
  • Date
  • Thread