[XML-SIG] foo.bar vs. foo.get_bar()

[uche.ogbuji@fourthought.com]

> On Fri, 5 Nov 1999 uche.ogbuji@fourthought.com wrote:
> > Yes, but a large part of the DOM REC can't be followed using pure attributes 
> > without __[g/s]etattr__.  I know that one can choose to implement subsets and 
> > approximations to the W3C DOM that don't run into such problems, but that 
> > doesn't suit everyone's needs.  Some of us are looking for full DOM 
> > compliance, and that's why we're dealing with these issues.
> 
> Woah. That's pretty annoying. Can you give an example of such an
> attribute?

Um, almost all DOM classes are affected.  From a brief survey of core

Node (attributes can raise exceptions)
NamedNodeMap (attributes can raise exceptions)
Attr (specified has rules about what must happen when user changes it)
ProcessingInstruction (attributes can raise exceptions)

I'm actually surprised that Element wouldn't require __[g/s]etattr__.  
However, the fact that Node does is the major damage.


-- 
Uche Ogbuji
FourThought LLC, IT Consultants
uche.ogbuji@fourthought.com	(970)481-0805
Software engineering, project management, Intranets and Extranets
http://FourThought.com		http://OpenTechnology.org