ACK!!!!! Re: [Zope3-checkins] CVS: Zope3/lib/python/Zope/App/OFS/Services/LocalEventService - LocalEventChannel.py:1.7 LocalEventService.py:1.11 ProtoServiceEventChannel.py:1.4 LocalServiceSubscribable.py:1.9 LocalSubscribable.py:1.7

[Ulrich Eck]

Hi Gary,

>> I'm sorry .. i didn't switch to the branch that i created,
>> I'll revert my changes in a minute in head and work in my
>> branch ..
>
Done.

>
> I'd be very interested in hearing about any practical problems you're
> encountering with the code or the approach; we can either fix it or
> decide to refactor/redesign if absolutely necessary.

with the current implementation: storing references/hardlinks of subscribers
an deliver events with ContextWrapper(subscriber, 
eventchannel).notify(event)
the receiving component is not notified within the right context.

It's possibly a security-problem and the current implementation of 
PathSubscriber
caches interface-info which might change over time, says steve.

It is impossible to use local Services when the eventservice is not within 
the
same servicemanger. I need this for my prototyping of a TaskSchedule that
starts a thread after it got an ZopeStartupEvent (another thing i'm working
on: LifeCycleEvents -> see proposals).

That's why i started a discussion in IRC today and steve suggested to use
location as subscriber-reference. the current implementation has now
two different mechanisms for global vs. local which i'm not happy with.

I looked at Zope.Events.ISubscribable and see what you mean. Are there
any details for the implementation or a branch that i could try?

or should implementations of subscribers that need to be called placefully
just use PathSubscriber for subscribing themselfs ??


Ulrich Eck
aka jack-e