Christopher Petrilli wrote:
Aside: Do you really need this within Zope if you can run a ZClient script with chron? While a scheduler within Zope isn't a bad idea, the infrastructure -- at least on Unix and NT -- is already there.
This probably shouldn't be inside Zope, as it could be pretty CPU intensive on occasion. The balance I would strike is to have an external application that uses ZClient to retrieve certain TYPES of objects and then works with them. Then you could manage it through the web, without having to have the actual threads inside Zope.
If someone uses this enough to hog down their machine, they they should probably be using ZEO with any number of processes running in the scheduler loop. Any very serious usage is probably not very smart usage unless you have the captal to back up the work with hardware. I like the whole idea, actually. I think a large number of test cases can be solved with cron, but others can't, and in the absence of a cross patform solution I like the idea of a standard component with a nice management interface. Getting back to to original idea for this whole thing is testing. An internal heartbeat system is not such a bad thing, in fact there is one but I don't think it's documented anywhere, it's a hack with zdaemon anyway. I think this could be handy. -Michel
Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli@digicool.com http://www.digicool.com
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )