> Ted, have you put some thought into what kind of API that should
> be on a Xerces2 based pull-parser? I would like to see an API
> that is simple enough to use for pull parsing but can communicate
> all of the information that XNI provides through its handler
FWIW, Microsoft has implemented a true pull-parser for their .NET
product. I wrote a code to use it, and it largely looks nice.
You can see the documentation at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemXmlXmlReaderClassTopic.asp
To view the list of all methods/fields, you can click "XmlReader members"
at the bottom of this page.
The problems of their design is:
- You have to call ReadStartElement and ReadEndElement for <foo></foo>.
This is fine. But you may not call ReadEndElement for <foo/>. (You
have to call ReadStartElement). This causes unnecessary trouble for
application.
- state transition chart of the parser would be really helpful.
regards,
--
Kohsuke KAWAGUCHI +1 650 786 0721
Sun Microsystems [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
