At 10:12 27/08/99 , Alexander Staubo wrote:
I agree that it would be nice -- I've been thinking of it earlier, then submitted to chron, because I'm lazy -- I'm just saying that we do have the tools, and running ZClient externally really isn't that different.
Ok, I'm sold.
I disagree slightly about your event object design though. Imho the event object should be similar to a DTML Method -- so the event "action" would in fact be DTML. The immediate benefit is that you can do anything -- you're not restricted to launching URLs, and you get the Zope context in the box. You could allow passing the calling event object to other parts of the site. If event objects descended from DTMLMethod, you could also use event objects just like DTML Methods and call them up -- manual execution if you will.
The scheduler should support concurrency, not just queueing. In fact, all we need is a simple "max concurrent tasks" semaphore to regulate the thread count from the master thread.
A scheduler also needs a logging/reporting system. A history API would be cool -- you could so <dtml-in "MyScheduler.pastEvents()"> and build your own schedule reports. Maybe all output from the event DTML should be attached to the history entry.
And so on.
Who writes this thing? This being an open source initiative(TM), I'm all for chipping in. Anyone want to join the Scheduler Task Force?
Well, we are getting a nice list of requirements already =). Anyone having some list space? Or shall we just move over to Zope-Dev? -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------