Ulrich, You may also be interested in http://cvs.zope.org/Products/Scheduler/ (it has a dependency on http://cvs.zope.org/Products/Event/ and a Zope
= than 2.6b1).
It relies on an external "clock" process to tickle it every so often, but you could of course kick off a Zope thread to do this... - C On Sun, 2002-10-13 at 11:44, Ulrich Eck wrote:
Hi there,
I just had an Idea and want to hear your comments on the following:
Zope is a Request-Based System. It has no internal scheduling functions except one installs Xron.
I have written a MicroThread Scheduler using python2.2 generators that supply cooperative Multithreading.
Now the point:
I want to integrate this Scheduler as one Thread (like Xron) to Zope as "Service" where clients could register a callback with parameters which are called regularly with a certain priority.
Zope's Persistent Object Database would morph to an completely persistent Program that handles requests too.
One could use it to implement better Workflow capabilities, or an Event Sytem (a client would register a Thread that checks for incoming messages and handles them). Many more things could be done ..
What are the pitfalls i can run into, when trying to implement this ?? I could think of concurrency issues, problem with threads, context, security .. any concrete hints ??
What do you think about that ??
Ulrich Eck ------------------------------------------------------------------------ net-labs Systemhaus GmbH Ebersberger Str. 46 85570 Markt Schwaben fon: +49-8121-4747-11 fax: +49-8121-4747-77 email: ueck@net-labs.de http://www.net-labs.de
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )