[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

java pull parser / fragment processing

• From: Stefan Haustein <stefan.haustein@t...>
• To: "xml-dev@i..." <xml-dev@i...>
• Date: Sat, 25 Dec 1999 04:00:39 +0100

Pull model based parsers offer several advantages 
when processing document fragments. The main
advantage is probably that a pull based parser
can be handed over between different fragment
processing entities without problems. Also,
the processing state can be encoded more naturally
in local variables etc. instead of having to
"find yourself" each time the handler is called.
Another advantage could be that namespaces (SAX2)
can be added without loosing compatibility since
all events need to be objects anyway. In contrast
to extending parameter lists, adding new methods
to objects does not destroy compatibility.

I have implemented a java xml parser following 
the pull model on top of a normal (push) SAX parser. 
If you are interested, please take a look at it.
It is available at http://www.trantor.de/saxpp
I am very interested if you think the interface is 
OK or if you have suggestions for improvements.

Best regards

Stefan

-- 
SAX-based access to WBXML and WML: www.trantor.de/wbxml

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: RE: Wish lists for the Holidays
• Next by Date: IE5 examples please...
• Previous by thread: Wish lists for the Holidays
• Next by thread: Re: java pull parser / fragment processing
• Index(es):
  • Date
  • Thread