Zope ClockServer Product

  The Zope ClockServer product provides a mechanism for users to call
  Zope object methods without the use of an external clock source
  (e.g. cron/wget).  It operates by acting as a medusa "server",
  essentially coopting Zope's asyncore mainloop and injecting "fake"
  requests into Zope's ZPublisher.  Despite the complicated
  description, it's rather easy to use.

Requirements

   Zope 2.7.X and UNIX (unless you can compile C extensions on
   Windows, too).

Installing the ClockServer product

   See INSTALL.txt

Configuring Your Zope Instance to Use the ClockServer Product

    In your Zope instance's "zope.conf" file place the following line
    in order to allow you to use the "clock-server" directive::

        %import Products.ClockServer

    Create a "clock-server" directive section anywhere beneath the
    import line, like so::

       <clock-server>
          method /do_stuff
          period 60
          user admin
          password 123
          host localhost
       </clock-server>

    Any number of clock-server sections may be defined within a single
    zope.conf.  Note that you must specify a username/password
    combination with the appropriate level of access to call the
    method you've defined.

    Descriptions of the values within the clock-server section
    follow:

       method -- the traversal path (from the Zope root) to an
       executable Zope method (Python Script, external method, product
       method, etc).  The method must take no arguments.

       period -- the number of seconds between each clock "tick" (and
       thus each call to the above "method").  The lowest number
       providable here is typically 30 (this is the asyncore mainloop
       "timeout" value).

       user -- a zope username.

       password -- the password for the zope username provided above.

       host -- the hostname passed in via the "Host:" header in the
       faux request.  Could be useful if you have virtual host rules
       set up inside Zope itself.

Making Sure the Clock Is Working

    Examine your Z2.log file.  It should show requests incoming via
    a "Zope Clock Server" useragent.

Reporting Bugs

   Use the Plope.com bugtracker at http://www.plope.com/software/collector

Other Contact

  Chris McDonough (chrism@plope.com)

Have fun!

- C
