Hi all, I'm trying to figure out the best use for an OOBTree, but I need some help.
I'm writing a framework around ZODB, this framework must have a hierarchy concept of users. Example: An application can manipulate objects A and B, I could have three users U1, U2 and U3. U1 and U2 read and modify different instances, U1 cannot read or modify U2 objects and vice-versa. U3, otherwise, is a parent of U1 and U2, and can read all his own children objects. My doubt is: Is it better: 1. to have a *big* OOBTree that collects all the objects, and then keep in U1 and U2 an OOBTee of ids referring the objects in the big one. 2. keep separate the U1 and U2 objects and let U3 search through all child OOBTree The second choice looks more simple to implement, but it increases the complexity of U1 searches. thank you for any ideas (and sorry for my poor English) david
signature.asc
Description: This is a digitally signed message part
_______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
