Well, that sort of makes sense.  The containing object is the object
that needs to be updated to rid itself of the reference to the contained
object.  I'm not sure I understand the problem.  The object to be
updated *is* the container.

>         My problem is the first step: how does the client recognize, which
> object has to be updated? In the case of a creation and deletion of an
> object, the transaction-class handles the parent object and not the object
> itself.

Chris McDonough
Digital Creations
Publishers of Zope - http://www.zope.org

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to