- From: Claude Zervas <claude@utlco.com>
- Date: Sun, 16 Aug 1998 23:48:47 -0700
- To: www-dom@w3.org
At 03:31 PM 8/16/98 +0200, ANOQ wrote: >... >1) Threadsafing/concurrency. Yes! Clearly defined behaviour when used in a multithreaded environment is a must. >2) Update notifications (events when the DOM-tree/text changes) The observer pattern is perfect for this. It should be possible for an observer to register itself with a document (or a node) to get change notifications. Node collections (ie NodeList) should have been defined this way so that 'liveness' is explicit (since it is not always needed). I would like to add a request to deprecate or at least make optional the Node.next/previousSibling attributes. These appear to be archaic scripting artifacts and should be replaced with the use of iterators. Cheers, - Claude Zervas
Received on Monday, 17 August 1998 02:39:41 UTC