Paul Winkler wrote at 2006-1-17 15:52 -0500:
> ...
>> An alternative would be a persistent subobject of the synchronized
>> object (such that its modification does not modify the
>> "bobobase_modification_time" of the primary object).
>That's not good: unless i find a suitable core zope class to use,
>if the user ever uninstalls ZSyncer, all of his objects are broken!

Maybe, a "PersistantMapping"?

>in general, i don't like to pile more data onto the poor user's
>unsuspecting objects. I have done it, i just don't like it :-)

Zope3 makes it a strategy (--> annotations),
CMF uses it a lot (--> WorkflowState, Discussability, ...)

Zope maillist  -
**   No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to