Thank you for your response.
My post was under the assumption that the deferred-node expansion makes
the underlying data structures "mutable' even though DOM is traversed in
a read-only way.
I understand that DOM REC does not talk about thread safety.
However it would be good if when the DOM is not modified, and
deferred-node expansion is off; the underlying data structures are
immutable. This way there can be immutable data objects whose getters
may traverse the DOM tree but still retain safety in concurrent access.
Thanks
Prashant
Joseph Kesselman wrote:
The FAQ[1], declares xerces DOM implementation is not thread safe.
Most DOMs are not threadsafe, as the DOM REC points out.
Threadsafety at such a low level of a system tends to be expensive and
redundant, and often insufficient since what you're concerned about is
safety over a complete transaction which may span multiple low-level
operations.
It is STRONGLY recommended that you implement your threadsafety at the
application logic level.
______________________________________
Joe Kesselman -- Beware of Blueshift!
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
