Hi, so if I do require thread safety for my application, what are the possible solutions (at least as far as xerces is concern). Will traversing the entire tree during the initialisation stage solve the problem?
Thanks. Cheers, Herry. --- Andy Clark <[EMAIL PROTECTED]> wrote: > Herry Koh wrote: > > thanks for the reply. So if I want to have > concurrent access to the > > DOM, I guess one way to do it will be to disable > the Deferred > > feature. The way to do it is clearly described in > the Xerces docs, > > You're missing the entire point. Please re-read > Elena's > post because she hits the nail right on the head. In > short, > you can *never* assume that any implementation of > the DOM > interface *guarantees* thread-safety. There's > nothing in > the spec that mandates it and it's just not smart > programming. > > This is not a deficiency or a bug in the Xerces DOM > impl. > And even in the non-deferred case, you should not > assume > that even read-only access is thread-safe. There may > be > (and probably are!) cases where the non-deferred DOM > impl > only creates objects (like node-lists, etc) when > they are > requested. This is simply done for performance and > is > completely allowed by the interface. > > -- > Andy Clark * [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________________________ Do You Yahoo!? Yahoo! Kickin' Party - Win a 5-star getaway to exotic Bali! http://kickin.yahoo.com.sg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
