Granted, nodelists are certainly not threadsafe. (And that's further complicated by their live-view behavior)
Last I looked, though, most of the basic Node accessors were ... well, not guaranteed threadsafe, but in the "if you don't care that the next version may break this assumption, you can get away with it" quasi-safe. If folks need more than that, they can (and should) either protect it at a higher level, or plug in a DOM implementation which has the required degree of safety. (It would be nice if that could be done by subclassing. Alas, subclassing DOMs becomes really ugly due to some of their internal behaviors, and it's usually easier to do a copy-and-alter pass.) ______________________________________ "... 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)
