Chris McDonough wrote:
On Sat, 2005-01-29 at 05:49, Andrew Veitch wrote:
I noticed there was a thread last month on an event service for Zope.
Did that reach any conclusion?
From what I can see the present products are:
- http://www.zope.org/Members/lstaffor/Xron - Zope 2.6 only, not being
Chris McDonough wrote:
On Sat, 2005-01-29 at 05:49, Andrew Veitch wrote:
I noticed there was a thread last month on an event service for Zope.
Did that reach any conclusion?
From what I can see the present products are:
- http://www.zope.org/Members/lstaffor/Xron - Zope 2.6 only, not being
Dylan Jay wrote:
Chris McDonough wrote:
On Sat, 2005-01-29 at 05:49, Andrew Veitch wrote:
I noticed there was a thread last month on an event service for
Zope. Did that reach any conclusion?
From what I can see the present products are:
- http://www.zope.org/Members/lstaffor/Xron - Zope 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dylan Jay wrote:
> Chris McDonough wrote:
>
>> On Sat, 2005-01-29 at 05:49, Andrew Veitch wrote:
>>
>>> I noticed there was a thread last month on an event service for
>>> Zope. Did that reach any conclusion?
>>>
>>> From what I can see the present p
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dylan Jay wrote:
+1 for using http://cvs.zope.org/Products/Scheduler
I think the time of a non-core scheduler needs to come to an end. Its
crazy the number of implementations out there.\
I'm using the zope cvs version and I've enh
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" - like schedule can be driven equally
well from ClockScheduler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dylan Jay wrote:
> Tres Seaver wrote:
>
>> 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" - like schedule can be driven equall
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.
It's fine with me. We maybe just need to remove the C extension in
it...
So to summarise:
- ClockServer is a good idea to put in the core but needs to made python
only.
- Schedular from cvs is probably the best one to use but not neccerily
in the core.
Does the schedular work with ClockServer by puting the notify path in
zope.conf or will the schedular need to b
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
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
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.
>
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
13 matches
Mail list logo
