-----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 equally >> well from ClockScheduler as from a separate thread. > > > So what's wrong with including ClockServer in the core or making it > easier to install? (ie not having to put packages in the python path > which is hard with some hosting arrangements)
Hmm, I thought I was arguing *for* including ClockServer in the core; what I don't want is some of the alternatives which rely on running special threads. > And what's the argument against a core scheduler regardless of a clock? > Isn't running background tasks a common need amoungst many very > different tools and therefore a interstructure issue? I could see including the Scheduler product as well, although there are some issues for "long-running" tasks which might not fit well (conflicts on the schedule itself are possible). Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC4Qr++gerLs4ltQ4RAg/BAKC9jzLSZ/CnMpDpKm7F+p2Wbm9CTACdEXgd c4gpIBSEXNa1gu3XDfF+JbQ= =DQrV -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )