On Tuesday 30 April 2002 11:16 am, Joseph Kesselman/CAM/Lotus wrote: > "SAX stream" -- Sorry about the shorthand; that phrase is sometimes used to > mean "sequence of SAX events". Basically, write code that issues the > appropriate SAX calls to drive a SAX2 ContentHandler. (You can think of > this as implementing part of the SAX XMLReader API.) >
What it looks like you are suggesting is essentially writing a SAX content handler that will write the xml to a file, and then manually generate the events to write the correct xml file. While this is interesting, and it is validating (which is cool, and something my lazy butt is unlikely to implement on my own), it isn't really an ideal solution. Furthermore, it still requires writing a stream that can output xml (of course a simple ostream would suffice, but . . .) I'll have to spend more time researching dom, as I've never needed the additional complexity dom requires. Thanks for the help, -- Brad Settlemyer http://deepcopy.org/ Progamming in the trenches --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
