question: NodeIterator in DOM
mcc at arbortext.com
Fri May 15 18:20:47 BST 1998
At 11:19 AM 5/15/98 -0400, Akitoshi Yoshida wrote:
>we have nodes A B C D E.
>the iterator is positioned just before C.
>remove C, D, and B.
>then we have A E and the iterator position should be
>positioned just before E.
>so toNextNode() and toPrevNode() should return E and A, respectively.
>NodeIterator may mark its current iterator position by
>an integer offset or by an object reference. but it must
>be notified for certain insert and remove operations to
>preserve the above semantics. Is it correct?
I'm not sure. There's been a lot of discussion of how to implement
NodeIterators on www-dom; see the archives at
I believe different designs exist, some of which require iterators to be
notified on insert and delete operations, and others which maintain
"markers" in the tree that move around as the tree is edited. I have not
followed this closely enough to give you a definitive answer, but look at
the www-dom archives, and especially Don Park's SAXDOM implementation,
because Don participated in the discussions of this a couple of weeks ago
and I believe his latest release reflects what he learned.
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev