OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: SAX Namespaces? ContentHandlers? Jobs.

[ Lists Home | Date Index | Thread Index ]
  • From: Ken MacLeod <ken@bitsko.slc.ut.us>
  • To: "Ean R . Schuessler" <ean@novare.net>
  • Date: 06 Apr 2000 11:29:03 -0500

[not having good answers handing for the rest of your questions, I'll
just try this one.]

"Ean R . Schuessler" <ean@novare.net> writes:

> So, thats one thing. Another thing that I'm confused about is how
> you communicate "out of band" or config data to a
> ContentHandler. XMLReader, obviously, has Features and Properities
> which are useful for telling it special things. How do you do
> similar things (querying capabilities, setting configuration data,
> etc.) on a Content Handler? Should it not be done? Should I make up
> my own API that will have to be replaced later?

SAX has an API for features and properties to allow multiple SAX
parser writers to share a "namespace" for feature and property names.

Since Handlers are generally application-specific and without multiple
implementations, there's rarely any contention for property names.

Just use standard techniques (your own API) for implementing Handler
properties, there shouldn't be any reason to replace it later.

  -- Ken

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS