Links

• Ben Hyde got the X-Ten Light VOIP phone working on the Mac. I tried it. I got it working to. Even talked to Ben to prove that the firewall traversal worked.

Notes

Sub Attributes

These are my thoughts from Katie's notes http://wiki.osafoundation.org/twiki/bin/view/Journal/KatieParlante20040427 on subattributes:

Creating a relationship Item is an alternate way of doing what ref collections do. The issue isn't with the construct as much as with the implementation, since ref-collections are implemented via b-trees in BerkeleyDB^?. There's enough reflection magic in Python, that this way of doing things could probably be made almost as succinct as what we have now. The big difference that I see is that having an Item for each relationship (which would correspond to an ItemRef^? in the existing repository implementation) allows that Item to have it's own attributes, which is not something that we can do with ref collections today. It's all a question of how meta we would like to go.

Ref-collections as Items -- I don't see this impacting the problems with subattributes either way (ref-collections are or are not Items). The problems that I see with sub-attributes mostly have to do with automatic maintenance of bi-directional references. We can certainly pick behaviors to reduce the ambiguities that I discussed in http://wiki.osafoundation.org/twiki/bin/view/Journal/TedLeung20040427, but my belief is that no matter which way we choose to resolve the ambiguity, a decent number of people will view the other (unchose) behavior to be more natural. If you make ref-collections Items, it looks like you could then do sub attributes by making sub-items of the ref-collection items, but that doesn't solve the reference maintenance problems, it just makes the sub-attributeness more familiar to a programmer coming from a language like Java.

-- TedLeung - 06 May 2004