DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6885>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6885 NodeImpl,ParentNode thread safety -- maybe a warning is in order? ------- Additional Comments From [EMAIL PROTECTED] 2002-03-05 20:39 ------- In general, the DOM APIs do not promise threadsafety. Unless a specific implementation actively promises that behavior, assume it isn't; any DOM operation may involve data caching or late retrieval or other reentrancy hazards. Remember, the DOM is only an API, not a specific set of classes; you have _NO_ way of knowing what's going on under the covers, only that it eventually returns data that represents a consistant DOM tree. (The DOM Working Group has reconsidered the threadsafety/locking issue periodically, but has generally come to the conclusion that locking should be performed at the application level for reasons of (a) efficiency and (b) atomicity of multiple-operation sequences.) So it isn't a bug unless the developers want to consider it so... but I agree that it might be worth reminding users about this, if a suitable place for that caveat can be found. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
