>Is the current stance a matter of principle (you don't believe the Xerces DOM should ever be made >thread-safe for read) or a practical constraint due to limited resources (you'd like the Xerces DOM to be >thread-safe, but other issues/enhancements have higher priority)?
My stance: I don't believe the Xerces DOM should be made thread-safe for read at the cost of making it slower, since most folks don't need that feature and there are other (and usually better) ways to achieve the same result. That's either a principled matter of practicality, or a practical matter of principle, take your pick. ______________________________________ "... 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)
