On 9/19/06, Chris Withers <[EMAIL PROTECTED]> wrote:
...because z has two containment paths:
x.z
x.y.z
...which might have different security constraints.
How does Zope 3 handle the same kind of setup?
In Zope2 containment is looked up through acquisition, that is,
implicitly. In Zope3 it is explicit, through the ILocation interface.
That interface specifies the __parent__ attribute, which normaly
specifies only one parent, as the current implementations of that
interface in Zope3 persist this or use a wrapper.
I a currently running application I store references to objects in
multiple places without problems just fine. Just be careful to clean
up when the object gets deleted from it's canonical location (the
__parent__ object).
--
Martijn Pieters
_______________________________________________
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
