Re: Thought on future of XMLC

> you would need to modify the DOM implementation such that it will be 
> aware if there was any change which the application does to the tree.

This is tracked by the LazyDOM already.

> Also you would need more information from the parsing process: When 
> the DOM is created you would need to store the beginning offset and 
> ending offset (from the original HTML string) within the DOM node.

There is no reason to do this. The information is already in the 
subtree of the node. However, using one long string and keep index into 
it may not be a bad idea. This would only increase the memory foot 
print by the size of file * 2 + 4 bytes * number of nodes. Hmm... looks 
more feasible now.

This would be some optimization to performance of LazyDOM. Can we start 
establishing some benchmark number for DOM so we know how much we gain 
from using different DOM implementation.

Mark, what do you think of this?


David Li
---
"It spells Mac OS X but pronounces NeXTSTEP"