Re: [Zope-dev] References, persistence, BTrees

2002-01-05 Thread kapil thangavelu
Hi jeffrey, perhaps it might save you a bit of trouble. i've written a publish/subscribe event channel that seems to have must of the functionality listed below although it does use the techniques that you wanted to avoid. its at http://www.zope.org/Members/k_vertigo/Products/EventChannel at

[Zope-dev] References, persistence, BTrees

2002-01-03 Thread Jeffrey P Shell
I'm experimenting with an event notification service based on a publish-subscribe model for some projects I'm working on. When a subscription comes in, a 'Subscription' object is made, that basically looks like this: class Subscription(Base): def __init__(self, subscriber, eventType,

Re: [Zope-dev] References, persistence, BTrees

2002-01-03 Thread Phillip J. Eby
At 05:49 PM 1/3/02 -0700, Jeffrey P Shell wrote: 'subscriber' is a reference to the subscribing object, and it's very likely to be to an object in the ZODB. Is it wise to have more than one persistent reference to a single persistent object? I swear that I had once heard Jim say (vocally)