> I've toyed with the idea of making a SAX-based version of the VOTABLE
> modules, but that would enatil a heavy redesign. In a perfect world, the
> user would be able to specify which type of parser (DOM or stream) it
> would like to use, and the objects in the VOTABLE::* hierarchy would act
> appropriately. It will have to happen eventually, for some value of
> eventually....
Definately, the entire point of using a VOTable toolkit instead of parsing the XML with a generic SAX or a DOM tool is that the user land code can (theoretically) be identical, and the underlying toolkit should take care of parsing the XML using either an event or tree based method depending on how/where its getting the XML.
Al.
-- Dr. A. Allan, School of Physics, University of ExeterReceived on 2003-10-23Z18:06:35