-----BEGIN PGP SIGNED MESSAGE-----
In article <001301bfc731$2af9c480$2101a8c0@pavilion>, Loren Stafford
<[EMAIL PROTECTED]> writes
>Yes. The Client.py patch must be applied for any use of ZScheduler, if the
>server is not listening on the default port.
The default port in Zope is 8080, whereas I recall seeing the bug
applies if not on 80.
>"reschedule" is always called when an event is triggered, so that there is
>an opportunity to reschedule or disarm the event. If "reschedule" fails (as
>it will if the server is not on the default port and the patch is not
>applied), the whole transaction fails.
Except that I scheduled a non-smtp event which worked fine without the
>By the way, what version of Zope are you using? I reported the bug in
>version 2.1.4. I wonder (because I haven't checked yet) if it was fixed in
Well, it's clear I need to install this patch and try again. I'm using
Regards, Graham Chiu
Powered by Interbase and Zope
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
-----END PGP SIGNATURE-----
Zope maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -