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: David Megginson <david@megginson.com>
  • Date: Mon, 17 Apr 2000 14:59:30 -0500

On Tue, Apr 11, 2000 at 04:20:40PM -0400, David Megginson wrote:
> See the SAX2 org.xml.sax.XMLFilter interface.

I am aware of this interface. Serializers do not tend to implement this
interface because they do not forward events, they do their job and 
serialize the data to some native format. My point being that most chains
start with a reader, connect to a series of filters and terminate with a
serializer. With the current API serializers cannot access the object that
is feeding them events because they have no way to obtain a reference to 
their parent. So, back to my original question, how does a serializer query
its upstream filters and readers for capabilities (ie. string-interning)?

Ean Schuessler                Director of New Products and Technologies
Novare International Inc.        The Unstoppable Fist of Digital Action
--- Some or all of the above signature may be a joke

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