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-06 00:32 ------- I agree that there's no claim of thread safety made. The assumption I had made for this code was the invariant provided by the non-synchronized java.util classes (e.g., HashMap, ArrayList) that read-only access was thread safe and that only modification of the structure required external synchronization. Obviously, that's not promised in this case, but, in general, that's a friendly stance. I propose a comment regarding multi-threaded access in the class documentation for ParentNode, at least. Also, if the developers were so inclined, they could provide thread-safe-on-readonly as an option, set by a feature. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
