• To: "Norman Walsh" <ndw@n...>,<xml-dev@l...>
• Subject: Re: JSR 206 and SAX
• From: "Jeff Rafter" <lists@j...>
• Date: Fri, 20 Feb 2004 13:07:52 -0800
• References: <87znbgt3nb.fsf@n...> <40341A54.40806@a...> <87n07elu8e.fsf@n...> <p06010203bc5acccee4c1@[192.168.254.4]> <014f01c3f73a$eb5b7830$6403a8c0@ARIMATHEA> <p06010205bc5af6249b29@[192.168.254.4]> <87n07d3bpq.fsf@n...>

> Our thinking was that normalization checking can be pretty expensive
> and you might want to have the factory return entirely different
> classes if the feature was enabled. Asking an XMLReader to reconfigure
> itself to do normalization checking seemed like it might be a burden.

I have to agree with Karl's point. In the case of AElfred2 it actually
provides two XMLReaders that can be used by a factory-- XmlReader, which has
validation support-- and SAXDriver, which has no validation support. It
seems like a good precedent.

Jeff Rafter

• References:
  • JSR 206 and SAX
    • From: Norman Walsh <ndw@n...>
  • Re: JSR 206 and SAX
    • From: David Megginson <dmeggin@a...>
  • Re: JSR 206 and SAX
    • From: Norman Walsh <ndw@n...>
  • Re: JSR 206 and SAX
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: JSR 206 and SAX
    • From: "Jeff Rafter" <lists@j...>
  • Re: JSR 206 and SAX
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: JSR 206 and SAX
    • From: Norman Walsh <ndw@n...>

• Prev by Date: Announcement: Last Call for W3C XQuery/Xpath2 formal semantics specification
• Next by Date: Re: SAX and XML Version
• Previous by thread: Re: JSR 206 and SAX
• Next by thread: Re: JSR 206 and SAX
• Index(es):
  • Date
  • Thread