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: "Ean R . Schuessler" <ean@novare.net>
  • To: Ken MacLeod <ken@bitsko.slc.ut.us>
  • Date: Thu, 6 Apr 2000 12:02:14 -0500

On Thu, Apr 06, 2000 at 11:29:03AM -0500, Ken MacLeod wrote:
> 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.

Well, here is a somewhat stupid example but an example none the less.
What if you want to do something like query a ContentHandler for its
underlying OutputStream, if it has one? Another application that would
be useful would be querying the "parent" of the ContentHandler for its
last modification time. The ContentHandler could then implement a very
efficient cache for whatever it is serializing the events to. With the
current SAX structure it is hard to see how this would be done.

Ean Schuessler                Director of New Products and Technologies
Novare International Inc.        The Unstoppable Fist of Digital Action
*** WARNING: This signature may contain jokes.

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