[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SAX: Next Round

• From: "Bill la Forge" <b.laforge@j...>
• To: "Lars Marius Garshol" <larsga@i...>, "XML Developers' List" <xml-dev@i...>
• Date: Fri, 22 Jan 1999 08:49:08 -0500

>I agree with this in the sense that the FilterManager should not be
>specified by SAX, however, the actual Filters themselves should, I
>think, be specified.
>
>The goal must be that both views should be supportable by any SAX
>Filter, allowing the same filters to be reused in MDSAX, Cowans model
>and in any other filter models that may spring up later.
>
>I think the best way to achieve this is to use interfaces that present
>different views of the Filter, essentially what I yesterday (yesterday
>for me, anyway :) called the 'separate interfaces' model.
>
>I'll see if I can find the time tomorrow to devise a design that
>allows this.


Lars,

I think the answer is staring us right in the face. Look at John's
ParserFilter:

public abstract class ParserFilter
 implements Parser, AttributeList,
 DocumentHandler, DTDHandler, EntityResolver, ErrorHandler {

• Follow-Ups:
  • Re: SAX: Next Round
    • From: John Cowan <cowan@l...>
  • Re: SAX: Next Round
    • From: Lars Marius Garshol <larsga@i...>

• Prev by Date: Why informal specs usually win
• Next by Date: namespaces and document structure [Re: Next Round]
• Previous by thread: Re: SAX: Next Round
• Next by thread: Re: SAX: Next Round
• Index(es):
  • Date
  • Thread