Thanks everyone who have replied with their valuable suggestions. We chose, for the moment, to go for mutex protected DOM tree. So far its been fine with out any cores.
Raju [EMAIL PROTECTED] wrote: > I have been sucessfully using the DOM and SAX API's in Xerces 1.6 in > multiple threads with no problems in production ready code, however, each > thread has been processing it's own document. Its kind of obvious that you > would not use multiple threads to process the same document (maybe as a > helper process given a Node List or Attribute list to work on). > > My $0.02 worth > > Sid > > -----Original Message----- > From: Joseph Kesselman/CAM/Lotus [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 18 April 2002 11:20 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: Is DOM tree thread safe for parallel reads? > > In general, the DOM API is not threadsafe. I think the DOM Working Group's > "open issues list" has a discussion of why -- basically, it's a lot of > overhead, and DOM-level threadsafety is generally not useful since most > apps where this is an issue really need to protect _sequences_ of DOM > operations. > > Last time I checked, the Xerces DOMs promised that separate Documents would > never interfere with each other but multithreaded access to a single > Document (and/or any of the nodes owned by it) was explicitly unsafe. I'm > not sure whether that's still the status in the most recent code. > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
