Thank you, Michael. I realize that this is more of a DOM problem rather than Xerces problem (and BTW - thank you and everybody out there for Xerces) but Xerces is an influential product and Xerces developers must be some of the best DOM experts that there are. So if you do not mind the question : what is your take on using DOM documents in multi-threaded environment? If general DOM discussion is off topic for you, I can also narrow this down to : what is the safe bet for cloning of documents in Xerces so that it is safe to use clones in different threads?
Regards Nikolay Michael Glavassevich-3 wrote: > > Hi Nikolay, > > nikolayo <[EMAIL PROTECTED]> wrote on 10/07/2008 > 08:48:21 AM: > >> 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? > > No development and unlikely to happen for the reasons Joe and I gave last > year when this thread was started. > >> 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). > > Should probably work with Xerces but no guarantee that it will work in > general. Aside from having no general guarantee of thread-safety, the > behaviour of cloneNode() [1] for the Document node is implementation > dependent. > >> Regards >> Nikolay > > Thanks. > > [1] > http://xerces.apache.org/xerces2-j/javadocs/api/org/w3c/dom/Node.html#cloneNode(boolean) > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [EMAIL PROTECTED] > E-mail: [EMAIL PROTECTED] > -- View this message in context: http://www.nabble.com/Making-Xerces-DOM-thread-safe-for-read-tp14230584p19950528.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]
