Sorry for resurrecting this but it is probably a very important issue for a
big
number of people who e.g. use DOM in JEE environment. My questions are :
1/ Is there any new development over the last year or so since the
discussion
occurred or is status unchanged?
2/ Is it at least thread safe approach to use cloned copies of Documents. If
I
provide multiple threads with copies generated from a single Document by
multiple calls to nodeClone() then can those threads safely use their
personal
cloned copies? For read only? For read/write? I think in this scenario
threads
should be granted full R/W ownership of their cloned copies but I do
not
know whether this is the case in Xerces (and I can imagine deferred
execution
implementations of cloneNode which would not provide this type of thread
safety).
Regards
Nikolay
Mark Goodhand-2 wrote:
>
> All,
>
> I understand that DOM provides no thread safety guarantees, and that
> the current Xerces implementation is not thread safe. I've seen the
> issue come up on the lists a few times over the past couple of
> years. As future hardware improvements are likely to come in the
> form of more cores rather than higher clock speeds, and with XML
> documents getting larger, I expect user requests for thread-safety
> (at least for unchanging documents) will only increase.
>
> As I understand it, it is performance-improving caches that prevent
> Xerces DOM from being thread-safe (for read). If true, this is
> ironic, considering the massive performance benefits that could come
> from parallel processing of documents.
>
> 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)?
>
> Regards,
>
> Mark.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Making-Xerces-DOM-thread-safe-for-read-tp14230584p19857414.html
Sent from the Xerces - J - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
