Hi all, In messages like http://www.mail-archive.com/zope3-dev@zope.org/msg05964.html, zc.async is mentioned as the solution for cron-like functionality in zope. Effectively you would not need zope2's clockserver. Reading zc.async's docs, I cannot find how to do a given task regularly. For example a weekly pack. Or a daily call of one method that archives older items. That sort of stuff. Many things can be handled by cronjobs, but you tend to get a lot of them. And you don't want to embed the password everywhere. Anyway: I cannot find the word "cron" anywhere in the zc.async source. Or "repetitive" or "regular". Is zc.async not intended for this kind of usage? Reinout -- Reinout van Rees - reinout@vanrees.org - http://reinout.vanrees.org Software developer at http://www.thehealthagency.com "Military engineers build missiles. Civil engineers build targets"
On Jun 24, 2009, at 1:19 PM, Reinout van Rees wrote:
Hi all,
In messages like http://www.mail-archive.com/zope3-dev@zope.org/msg05964.html , zc.async is mentioned as the solution for cron-like functionality in zope. Effectively you would not need zope2's clockserver.
Reading zc.async's docs, I cannot find how to do a given task regularly. For example a weekly pack. Or a daily call of one method that archives older items. That sort of stuff. Many things can be handled by cronjobs, but you tend to get a lot of them. And you don't want to embed the password everywhere.
Anyway: I cannot find the word "cron" anywhere in the zc.async source. Or "repetitive" or "regular". Is zc.async not intended for this kind of usage?
Hi Reinout. zc.async can be used to do cron-like activities by starting a job, to be performed after a certain time, that has a callback that reschedules another job when desired. This has the advantage over cron-like behavior because it does not reschedule until the first job is done. Other zc.async competitors have cron implemented more directly, but I found it to be very easy and flexible to do what I wanted using the zc.async approach. Gary
On 2009-06-24, Gary Poster <gary.poster@gmail.com> wrote:
zc.async can be used to do cron-like activities by starting a job, to be performed after a certain time, that has a callback that reschedules another job when desired.
This has the advantage over cron-like behavior because it does not reschedule until the first job is done.
Well, for a task that runs a couple of seconds once a day or once a week... My first thought was "if something goes wrong, the chain is broken and no new jobs will be scheduled anymore". From the documentation, it seems zc.async is pretty robust so this is probably not something I have to worry about. I'd put a short paragraph in the readme that this is how you can do cron jobs. Helps with the google for "zope cron", too :-)
Other zc.async competitors have cron implemented more directly, but I found it to be very easy and flexible to do what I wanted using the zc.async approach.
Thanks for the info. I'll see if I can get a basic cron-with-pack setup in one instance running. Reinout -- Reinout van Rees - reinout@vanrees.org - http://reinout.vanrees.org Software developer at http://www.thehealthagency.com "Military engineers build missiles. Civil engineers build targets"
Am Mittwoch 24 Juni 2009 19:19:17 schrieb Reinout van Rees:
Hi all,
In messages like http://www.mail-archive.com/zope3-dev@zope.org/msg05964.html, zc.async is mentioned as the solution for cron-like functionality in zope. Effectively you would not need zope2's clockserver.
Reading zc.async's docs, I cannot find how to do a given task regularly. For example a weekly pack. Or a daily call of one method that archives older items. That sort of stuff. Many things can be handled by cronjobs, but you tend to get a lot of them. And you don't want to embed the password everywhere.
Anyway: I cannot find the word "cron" anywhere in the zc.async source. Or "repetitive" or "regular". Is zc.async not intended for this kind of usage?
I personally recommend to also look at lovely.remotetask, as this does have direct cronjob functionality and is relatively simple to implement. I personally use it, however, I'm still a bit sceptic if it's really robust and scales well, moreover, I'm unsure if it is actively maintained. Best Regards, Hermann -- hermann@qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7
On Thu, 2009-06-25 at 13:05 +0200, Hermann Himmelbauer wrote:
Am Mittwoch 24 Juni 2009 19:19:17 schrieb Reinout van Rees:
Hi all,
In messages like http://www.mail-archive.com/zope3-dev@zope.org/msg05964.html, zc.async is mentioned as the solution for cron-like functionality in zope. Effectively you would not need zope2's clockserver.
Reading zc.async's docs, I cannot find how to do a given task regularly. For example a weekly pack. Or a daily call of one method that archives older items. That sort of stuff. Many things can be handled by cronjobs, but you tend to get a lot of them. And you don't want to embed the password everywhere.
Anyway: I cannot find the word "cron" anywhere in the zc.async source. Or "repetitive" or "regular". Is zc.async not intended for this kind of usage?
I personally recommend to also look at lovely.remotetask, as this does have direct cronjob functionality and is relatively simple to implement. I personally use it, however, I'm still a bit sceptic if it's really robust and scales well, moreover, I'm unsure if it is actively maintained.
At least we are using it actively in different projects and keep updating it. The original lovely team has become a bit silent lately, but as I can see at least Zagy has the right to upload releases to PyPI. Christian -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
participants (4)
-
Christian Theune -
Gary Poster -
Hermann Himmelbauer -
Reinout van Rees