Lists Home |
Date Index |
- From: Tyler Baker <firstname.lastname@example.org>
- To: John Cowan <email@example.com>
- Date: Thu, 17 Sep 1998 18:54:24 -0400
John Cowan wrote:
> Tyler Baker wrote:
> > Sorry my confusion lies in that parsing refers to taking data of one unmanageable
> > form and converting it into a manageable form.
> > Parsing a DOM tree is an oxymoron IMHO unless
> > you are converting the DOM tree into some other tree.
> No, what I have is code that converts a DOM *tree* into a
> SAX *event stream*. The result is "manageable" to applications
> that expect SAX events.
Ahh, I see. In this sense I suppose it is a parser. I suppose I just was not sure
what you meant at first. In this case you have a DOMSAX for better lack of a term. I
can see how this would be useful to apps that build a DOM tree straight out of a
database and then need to have the data be sent into some XML framework without having
to first write the contents of the DOM tree out to a stream and then read it in the
output as input into a SAX compliant parser.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)