[Zope] ZScheduler

[Loren Stafford]

You're right. I should have said port 80 instead of default port. I was
thinking of the system "default" for HTTP which is 80. In any case you need
the patch.

-- Loren


----- Original Message -----
From: "Graham Chiu" <anon_emouse@hotmail.com>
To: <zope@zope.org>
Sent: May 26, 2000 12:10 PM
Subject: Re: [Zope] ZScheduler


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In article <001301bfc731$2af9c480$2101a8c0@pavilion>, Loren Stafford
> <lstaffor@dynalogic.com> 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
> patch.
>
> >
> >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.
>
> Well, it's clear I need to install this patch and try again.  I'm using
> 2.1.4.
>
> - --
> Regards,  Graham Chiu
> gchiu<at>compkarori.co.nz
> http://www.compkarori.co.nz/index.php
> Powered by Interbase and Zope
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGPsdk version 1.7.1
>
> iQA/AwUBOS4xebTRdIWzaLpMEQIPWwCg5uZpGCphTW2SAnYt0nHBQ6m5IgsAn2xW
> 4n4onec3rtzBnz9ZB3SRmuzc
> =5YOQ
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> 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 )
>