Along this lines, there are thread save read-only XML tree models available, just not DOM. Saxon's tree model is thread safe during read operations. I believe XOM is as well (not 100%).
---------------------------------------- David A. Lee d...@calldei.com http://www.xmlsh.org -----Original Message----- From: Mukul Gandhi [mailto:muk...@apache.org] Sent: Thursday, June 09, 2011 1:06 AM To: j-users@xerces.apache.org Subject: Re: DOM thread safety issues & disapearring children On Wed, Jun 8, 2011 at 7:29 PM, Newman, John W <newma...@d3onc.com> wrote: > > ~100 users at the same time, a percentage of which are reading the same node > and slicing through its children. It seems, that all your users are concurrently accessing an in-memory DOM tree for read access, and it seems that non thread-safety of DOM implementation (and has been said, that DOM spec doesn't recommend thread safety for implementations; and I agree with Joe's remarks with this regard) is causing troubles for you. Perhaps you may need to re-look at the data model & storage design of your application. You may consider using some form of RDBMS storage (and/or coupled with XML storage). Or a quick fix may be to, try for a better concurrency/locking programming within your application. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
