[Zope3-dev] Re: principal events for the event hub
Ronald L Chichester
complaw@hal-pc.org
Wed, 07 May 2003 16:01:11 -0500
I may be out of step here, but...
Would it be better to have two categories of events? The
first category would be those events that are undertaken
immediately. The second category would be those events
that are undertaken periodically (ala cron.hourly,
cron.daily, cron.weekly, etc.). You could then write a
specific thread for the periodic events and allocate
(more/less) resources accordingly at that specific time.
That might take some of the sting out of the scalability
issue.
Many of the events that I envision for my applications
fall into the periodic category. Something akin to a cron
job would be welcome. I suspect the same is true for
other users.
Just a thought...
Ron
On Wed, 07 May 2003 16:22:06 -0400
Jim Fulton <jim@zope.com> wrote:
>Steve Alexander wrote:
>>Chris Withers wrote:
>>
>>>Do we really want this many messages floating around Zope
>>>3?
>>>
>>>I know we're aiming to be slow^w^w^w^wnot aiming to be
>>>optimised, but
>>>how will we ever make a system with myriads of events
>>>flowing around
>>>scale properly?
>>
>>
>>How do you expect a system to scale properly if it
>>doesn't use some form
>>of abstraction and decoupling?
>
>Chris wasn't suggesting that we have no form of
>abstraction and
>decoupling. I don't think he meant to imply that we
>wouldn't use events.
>
>Christian's proposal has an event for *every* object
>access. That is
>*a lot* of events. I think that that is an unreasonably
>large number of
>events. I would not want to generate that many events by
>default, especially
>since there wasn't a reasom given for why they are
>necessary.
>
>Having said that, if someone *did* need that level of
>notification
>(e.g. for super anal auditing) they could install a
>custom security policy
>that generated the events.
>
>Of course, you'd need to make sure that you didn't
>generate events for the
>security checks to make sure the events could be
>accessed. :)
>
>Jim
>
>--
>Jim Fulton mailto:jim@zope.com Python
>Powered!
>CTO (703) 361-1714
> http://www.python.org
>Zope Corporation http://www.zope.com
> http://www.zope.org
>
>
>
>_______________________________________________
>Zope3-dev mailing list
>Zope3-dev@zope.org
>http://mail.zope.org/mailman/listinfo/zope3-dev