- From: Fred L. Drake, Jr. <fdrake@acm.org>
- Date: Fri, 20 Apr 2001 15:40:15 -0400 (EDT)
- To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
- Cc: "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>, "'www-dom@w3.org'" <www-dom@w3.org>
Arnold, Curt writes: > Follow up to: > http://lists.w3.org/Archives/Public/www-dom-ts/2001Apr/0030.html > http://lists.w3.org/Archives/Public/www-dom-ts/2001Apr/0032.html ... > Does (or should) DOM 3 address this by adding a getMutex() or > similar method, something like: I'll chime in to note that the DOM currently does not (as far as I can tell) have anything to say about concurrency. In particular, it does not require or imply that support for concurrent operation is required. I think this is a good thing. While I think I understand your interest, it's not clear to me that the DOM needs provide direct support for concurrency-related issues. If something like this is required, the specification should at least make it clear that the getMutex() can return null -- not all environments support concurrency, or an implementation may not want to provide explicit support for it. Perhaps you need to present your motivation for using the DOM nodes as synchronization objects independently from Java -- the idiom of using an arbitrary object for synchronization is not used in all languages. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations
Received on Friday, 20 April 2001 15:40:43 UTC