Standard response: Making every DOM operation thread-safe would impose overhead on tasks which don't require it, would be less efficient than locking at a higher level of your application, and in fact would be less APPROPRIATE than locking at a higher level of your application since in general the things you actually want to guarantee threadsafety for involve multiple DOM operations.
Hence, the DOM Working Group recommended that you implement threadsafety in the code which uses the DOM rather than in the DOM itself. ______________________________________ "... 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)
