The DOM is not promised to be threadsafe. The Xerces DOMs are not designed to be threadsafe; they are designed to be reasonably fast and compact.
The fact that Node read access happens to be safe in one of our DOM implementations does not require that Nodelist also be made safe -- and in fact it isn't guaranteed that Node access will stay threadsafe either, though I don't expect that to change any time soon. If you need threadsafety, it's up to you as a code designer to either obtain and plug in another DOM implementation which does guarantee that, or to implement the locks at the application-code level. I strongly recommend the latter, since performance and code robustness is likely to be better, but you're free to select either. ______________________________________ "... Three things see no end: A loop with exit code done wrong, A semaphore untested, And the change that comes along. ..." -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html)
