Re: [Zope-dev] Re: Event & Timer Service for Zope 2.8

2005-07-25 Thread Chris McDonough
On Tue, 2005-07-26 at 09:44 +1000, Dylan Jay wrote: > So to summarise: > > - ClockServer is a good idea to put in the core but needs to made python > only. Yes, at least for inclusion into Zope. > - Schedular from cvs is probably the best one to use but not neccerily > in the core. Not sure a

Re: [Zope-dev] Re: Event & Timer Service for Zope 2.8

2005-07-24 Thread Chris McDonough
On Sun, 2005-07-24 at 11:51 +1000, Dylan Jay wrote: > Chris McDonough wrote: > > On Fri, 2005-07-22 at 13:11 +0200, Florent Guillaume wrote: > > > >>Dylan Jay <[EMAIL PROTECTED]> wrote: > >> > >>>Tres Seaver wrote: > > >>Myself I'm for having ClockServer in the core, if Chris and others agree. >

Re: [Zope-dev] Re: Event & Timer Service for Zope 2.8

2005-07-23 Thread Chris McDonough
On Fri, 2005-07-22 at 13:11 +0200, Florent Guillaume wrote: > Dylan Jay <[EMAIL PROTECTED]> wrote: > > Tres Seaver wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > > Chris' ClockServer removes the need for such a thread, by hooking > > > ZServer's mainloop to generate the

Re: [Zope-dev] Re: Event & Timer Service for Zope 2.8

2005-07-22 Thread Florent Guillaume
Dylan Jay <[EMAIL PROTECTED]> wrote: > Tres Seaver wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > Chris' ClockServer removes the need for such a thread, by hooking > > ZServer's mainloop to generate the "faux" request needed to kick off > > async processing. A "crontab" - lik