> Is there any thread-safe way to *read* a DOM from
> multiple threads simultaneously?
The only guaranteed-portable answer is to set up your own locks to ensure
only one thread tries to access the DOM at a time. The DOM WG looked at
this and decided that locking on individual DOM operations was both
overkill (most folks don't need it) and inadeqaute (since usually if you're
concerned about multithreading you want to lock on higher-level operations
instead, for reasons of both efficiency and atomicity).
If you're unwilling to do it that way ... as of the last time I looked, the
Xerces non-deferred DOM implementation was threadsafe under read.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
