Re: Re[2]: Thought on future of XMLC

Jake,

  Thanks for the pointer.

  However, this isn't quite the same as the LazyDOM. The event based  
processing in DOM4J is to handle the processing of large document by  
not keeping all of them in memory. Similar to SAX approach.

  What LazyDOM does is actually build a full DOM tree of the document  
in memory and provide copy on modification. In the XMLC programming  
model, a new document object is created, modified, and output. Without  
LazyDOM, a new document has to be built everytime. LazyDOM improve the  
performance by letting all document objects for the same document  
sharing the same DOM and only the modified nodes are copied in the  
particular instance. By doing so, time is saved in the construction of  
the tree and less node object creation in each of the new document. The  
conservation of memory is just a side effect. :)

David

On Thursday, Nov 21, 2002, at 02:04 Asia/Shanghai, Jacob Kjome wrote:

> Hello David,
>
> I believe DOM4J provides some functionality similar to LazyDOM:
>
> http://www.dom4j.org/ 
> faq.html#How%20does%20dom4j%20handle%20very%20large%20XML%20documents?
>
> Jake