xml-dev - Ignorant and obsolete criticisms of SAX2 (probably)

["Ean R . Schuessler" <ean@novare.net>]

Hi,

Sorry for my late arrival. I've been slow to get on this xml-dev list
thingy. I have a few questions about the SAX2 API. I hope you ladies
and gents can help set me straight.

1. Why are there both features and properties? Can't a Feature be
   modeled as a Boolean form of a Property? Doesn't this more accurately
   represent the situation of Features that are recognized but not
   present? (ie. False but not null)

2. What is the suggested way for handling request specific metadata
   from the containing application context? More simply, if I am going
   to generate an InputSource from a HttpServletRequest how should I
   provide SAX Filters/Readers access to the HttpServlet objects? Should
   I set them as a Property in the Reader? That seems a bit awkward
   since that means you have to rewrite a FileReader for every type of
   application context you might want to use one in. Wouldn't it be
   more elegant to implement the Properties interface on the 
   InputSource itself?

3. Since an XMLReader is a thing which has no SAX parent because it 
   reads from a native format, shouldn't an XMLWriter be a thing
   which has no SAX children because it writes to a native format?
   Shouldn't SAXFilter then be the aggregate of those two
   interfaces?

4. If it makes sense to query up the SAX chain to detect
   capabilities in parents, shouldn't you also be able to query
   down the SAX chain to detect capabilities in children? This
   would seem especially useful with regard to Filters that
   generate inlined code wanting later compilation.

I thought I had some more questions, but that is all I can recall
right now. So, apologies for the clueless arrival. Bash at will.

E

-- 
___________________________________________________________________
Ean Schuessler                                                Freak
Novare International Inc.                             Freak Central
--- 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/
***************************************************************************