W3C home > Mailing lists > Public > www-di@w3.org > June 2005

[DPF] 4.3.2 exception on removal

From: Keith Waters <kwaters@ftrd.us>
Date: Fri, 3 Jun 2005 13:58:36 -0400
Message-Id: <1873CEE6-F5C4-451A-AF2B-AFC8407247C1@ftrd.us>
To: www-di@w3.org

Hi Jeremy,

This message contains a response to comments on


4.3.2 exception on removal better?

I was surprised that accessing a property that has been deleted is
not an exception. If the WG has already considered and rejected such
a design choice, this comment is already adequately addressed. Otherwise
please consider it.

The DPF Working Group did consider this issue relating to properties  
within a DPFPropertyList. When the property list needs to be live,  
this poses certain problems. Considering the issues that may be  
raised, it was decided that the best way to maintain the states  
within the property list would be to point a property entry to a NULL  
node if it was removed. If the value of the node was accessed by the  
calling application and then the property was removed (thereby the  
application uses the stored value to access it again), then an  
INVALID_ACCESS_ERR exception would be raised.

-Keith Waters
Received on Friday, 3 June 2005 17:58:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:54:24 UTC