Lists Home |
Date Index |
- From: "Borden, Jonathan" <firstname.lastname@example.org>
- To: "XML Developers' List" <email@example.com>
- Date: Wed, 3 Feb 1999 23:35:03 -0500
Clark Evans wrote:
> DOM requires the entire stream be read before the
> the document object is returned and processing can begin.
> Not only does this chew significant memory for very large
> streams, but it causes significant delay before output
> could be generated. In the worst case, it turns a
> perfectly simple problem into an "impossible" one
> where the memory requirements and time delay make
> the solution useless.
You are missing the point. Since the data is already deserialized, there is
no delay due to processing. The idea is that the data has already been
entered into a database which implements a DOM interface (the database is
free to implement other interfaces as well). I never claimed that the data
was entered as XML or that a serialized XML document ever existed.
Your entire argument assumes that there is a need to parse XML into an
in-memory DOM during the processing phase. This is incorrect.
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/ and on CD-ROM/ISBN 981-02-3594-1
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)