Yes, using Client.py was the easiest way to do that. The biggest problem
with Client.py is its dependency on HTTP. If your server is set up to
only accept HTTPS, then you can't use Xron -- not a desirable trade-off.
If security is the problem, you could configure the HTTP part to
listen only on
From: "Kapil Thangavelu" [EMAIL PROTECTED]
[snip]
Xron has a single dispatcher thread. This thread knows how long to
sleep
for until the next job needs to run.
this model has problems when new jobs (for immeadiate execution) are
entered after the system sleeps. i think it should it
What if you want a small job to be done every 30 seconds?
I generally don't... I'm satisfied with cron granularity, although
others
might not be. Do you have this requirement?
I thought a little about the granularity issue and decided to go with
the most general solution. I have no
The Xron product seems rather "fragile" in use.
That is, if things go wrong when an Xron DTML Method is triggered, that
method doesn't get rescheduled.
An example of this is that my intranet DNS server needed to be rebooted.
Xron couldn't look up the appropriate domain name, and stopped
Steve,
I am also interested in scheduling... though I haven't looked closely at
Xron.
The Xron product seems rather "fragile" in use.
That is, if things go wrong when an Xron DTML Method is triggered, that
method doesn't get rescheduled.
Does Xron take an optimistic approach to repeating
Chris McDonough wrote:
Steve,
I am also interested in scheduling... though I haven't looked closely at
Xron.
The Xron product seems rather "fragile" in use.
That is, if things go wrong when an Xron DTML Method is triggered, that
method doesn't get rescheduled.
Does Xron take
Chris McDonough wrote:
As a side note, I do not like the fact that Xron requires you to use special
DTML methods. I suppose this is a requirement in this architecture due to
the fact they need to be autocataloged, but I don't really like that feature
either :-).
I think Xron could work
As a side note, I do not like the fact that Xron requires you to use
special
DTML methods. I suppose this is a requirement in this architecture due
to
the fact they need to be autocataloged, but I don't really like that
feature
either :-).
I think Xron could work with anything that has
I'll need to try to call get_transaction().commit() from a
manually-constructed Python thread fired off from Zope and see what
happens.
I think it'll just work. I'll find out in a few minutes. :-)
Yes, it just works. :-)
___
Zope-Dev maillist
Do you think this is this any more effective than having a producer
thread
do a lookup every minute to see what jobs are current, after which it
should
put the current jobs in a queue? E.g., as the "run" method of a
separate
producer thread:
the same problem applies, a solution might
10 matches
Mail list logo