From: Tres Seaver [mailto:tseaver@palladion.com]

Hmm, I guess I don't see the necessity of making it a Singleton here. Suppose you need to segregate events into separate priority classes, or guarantee that, when executed, the run with the permissions of different users? Splitting up the schedule _might_ not be a terrible thing to do. Your default case could then just require dropping a single instance of the Schedule class at the root of your Zope hierarchy, and leaving it there.

As an extra note: Security can be taken care of by using a Proxy role on the Event, or by adding support for a username/password propery combo (Events are called using ZClient, because the Events have to be called independent of current web requests, and you do need a HTTP REQUEST context). -- Martijn Pieters, Software Engineer | Digital Creations http://www.digicool.com | Creators of Zope http://www.zope.org | mailto:mj@digicool.com ICQ: 4532236 | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 -------------------------------------------