Yes. The Client.py patch must be applied for any use of ZScheduler, if the
server is not listening on the default port.

"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.

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
later versions.

-- Loren

----- Original Message -----
From: "Graham Chiu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: May 25, 2000 11:11 PM
Subject: Re: [Zope] ZScheduler


> In article <019501bfc6c2$91e19b60$2101a8c0@pavilion>, Loren Stafford
> <[EMAIL PROTECTED]> writes
> >Graham,
> >
> >Thanks for sending all the info. I haven't had a chance to check it all
out.
> >But I want to ask one more thing: did you install the patch to client.py
as
> >mentioned in CHANGES.txt and
> >http://www.zope.org/Members/lstaffor/ZScheduler/ZSchedulerWiki/BugReports
> >
>
>
> Loren,
>
> Since this bug referenced a reschedule operation, I didn't bother to
> apply the patch - should I?
>
> --
> Regards,  Graham Chiu
> gchiu<at>compkarori.co.nz
> http://www.compkarori.co.nz/index.php
> Powered by Interbase and Zope



_______________________________________________
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to