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

Re: Reusing, Refactoring, Reinventing??? (was Re: SA

• To: xml-dev@l...
• Subject: Re: Reusing, Refactoring, Reinventing??? (was Re: SAX for Binary Encodings (SAD-SAX)
• From: Fredrik Lindgren <fredrik.lindgren@c...>
• Date: Sun, 09 Nov 2003 23:53:15 +0100
• Cc: bob@w...
• In-reply-to: <001b01c3a703$86eb1680$650aa8c0@BOBDEV>
• Organization: Fredrik Lindgren
• References: <001b01c3a703$86eb1680$650aa8c0@BOBDEV>
• Reply-to: fredrik.lindgren@c...
• User-agent: Opera7.21/Win32 M2 build 3218

Just a small request for clarification regarding how the 
TypedContentHandler behaves exactly as the current ContentHandler:

If the TypedContentHandler works exactly as a ContentHandler, I assume the 
following scenario should work:

- Create a Filter F that passes all supported events to the next layer 
unchanged, but exposes a TypedContentHandler instead of the ordinary 
ContentHandler to the underlying XMLReader. (This could be just for 
logging purposes or whatever).

- Put this filter between an old style ContentHandler C and the type-aware 
XMLReader.

Is it your opinion that C would receive the same events from the filter as 
it would if it was connected directly to the XMLReader?

If you put an identity filter into the chain using the current SAX 
architecture you would get the same events. I fear that a type-aware 
XMLReader would use the additional call in the TypedContentHandler, and 
leave out the calls for the underlying elements and attributes that the 
XMLReader interpret as a typed object.

Please explain how the parser would both give the TypedContentHandler it's 
typed data and fulfill the expectations of the ContentHandler interface 
with regard to elements and attributes.

/Fredrik Lindgren

On Sun, 9 Nov 2003 15:53:28 -0500, Bob Wyman <bob@w...> wrote:


> 	Right. TypedContentHandler works exactly like ContentHandler
> except that it can do just a little bit more. This is reuse of the
> interface (and much, but not all, of the implementation as well). The
> contract presented by TypeContentHandler is precisely the same as the
> contrat presented by ContentHandler -- except that TypedContentHandler
> can do a little more. Its like if you create a "Person" class and then
> created "Man" and "Woman" subclasses that can do specific things that
> the generic "Person" doesn't do to well. This is classic computer
> science...
>
> 		bob wyman
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>



-- 
Fredrik Lindgren

• Follow-Ups:
  • RE: Reusing, Refactoring, Reinventing??? (was Re: SAX for Binary Encodings (SAD-SAX)
    • From: "Bob Wyman" <bob@w...>

• References:
  • RE: Reusing, Refactoring, Reinventing??? (was Re: SAX for Binary Encodings (SAD-SAX)
    • From: "Bob Wyman" <bob@w...>

• Prev by Date: Re: Production 78 / Process failure in XML 1.1
• Next by Date: Re: SAX for Binary Encodings (SAD-SAX)
• Previous by thread: RE: Reusing, Refactoring, Reinventing??? (was Re: SAX for Binary Encodings (SAD-SAX)
• Next by thread: RE: Reusing, Refactoring, Reinventing??? (was Re: SAX for Binary Encodings (SAD-SAX)
• Index(es):
  • Date
  • Thread