In general, the DOM API is not threadsafe. I think the DOM Working Group's "open issues list" has a discussion of why -- basically, it's a lot of overhead, and DOM-level threadsafety is generally not useful since most apps where this is an issue really need to protect _sequences_ of DOM operations.
Last time I checked, the Xerces DOMs promised that separate Documents would never interfere with each other but multithreaded access to a single Document (and/or any of the nodes owned by it) was explicitly unsafe. I'm not sure whether that's still the status in the most recent code. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
