[
Lists Home |
Date Index |
Thread Index
]
- From: David Megginson <david@megginson.com>
- To: xml-dev@xml.org
- Date: Mon, 17 Apr 2000 16:18:37 -0400 (EDT)
Ean R . Schuessler writes:
> 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)?
If the serializer is an integral part of the application, then the
application can provide it with a reference to the XMLReader; if the
serializer is part of a library, then it can extend the XMLFilter
interface, or the application can pass information on to it through
additional setters.
All the best,
David
--
David Megginson david@megginson.com
http://www.megginson.com/
***************************************************************************
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/
***************************************************************************
|