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

Fw: SAX: Next Round

  • From: "Bill la Forge" <b.laforge@j...>
  • To: "John Cowan" <cowan@l...>
  • Date: Fri, 22 Jan 1999 11:55:11 -0500

Fw: SAX: Next Round
John,

Looks like the list server chopped things off when a '.' was the only thing
on the line.

Bill
-----Original Message-----
From: Bill la Forge <b.laforge@j...>
To: Lars Marius Garshol <larsga@i...>; XML Developers' List <xml-dev@i...>
Date: Friday, January 22, 1999 8:49 AM
Subject: Re: SAX: Next Round


>>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 {
>.
>.
>.
>}
>
>Now that's a lot of interfaces. Lets say we simplify this just a tad...
>
>public abstract class Filter
> implements Parser, DocumentHandler, DTDHandler, EntityResolver, ErrorHandler {
>
>        public Filter()
>        {
>        }
>
>        public void setSourceParser(Parser sourceParser)
>        {
>                sourceParser.setDocumentHandler(this);
>                sourceParser.setDTDHandler(this);
>                sourceParser.setEntityResolver(this);
>                sourceParser.setErrorHandler(this);
>        }
>
>        public void setDestinationFilter(Filter destinationFilter)
>        {
>                destinationFilter.setSourceParser(this);
>        }
>
>}
>
>This is a minor generalization of ParserFilter which could also serve as a 
>basis for MDSAX.
>
>Bill
>


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/
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...)


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.