How to create a background process

TEDennis tedennis at softwaredetails.com
Sun Sep 27 14:55:38 EDT 2009




Josep wrote:
> 
> Hi,
> 
> I experimented with the send in time command.
> I need to program some tasks to run at fixed time and days. Like schedule 
> a task for a backup for example.
> How can control this? Any experience?
> And how lunch these task in the way that don't stop or delay the
> app and/or system?
> 
> My idea is to program the time that the task must
> be run. When the app is lunched I check thr task for day and 
> "send in time" the task.
> The task will be executed by a standalone stack.
> The task are backups and calculate grand totals.
> 
> By other way a lunch speak messages to the user, but if one message is
> runnig
> and one second message start, the first is stoped.
> How wait until the revspeak finish before start the next?
> I tryed from a custom message and using wait for message but doesn't work.
>  
> Thoughts?
> 
> Salut,
> Josep
> 

A heads-up, just in case it happens to you, too.

I've had difficulties with the "Send in time" process.  As long as the Rev
task is the only Vista task running, it works fine.  ie: it can run all
weekend, firing itself every nn minutes (15 or less depending on context).

However, during the week when I am using my PC to do other things at the
same time (multiple browser sessions, for instance), the message I "sent in
time" doesn't always get triggered.  I have to manually restart it.  I don't
know what causes that to happen.  I have spent an hour or two trying to
track it down, but since the task is not critical to my daily operations, I
just ignore the problem and restart it manually.  It's frustrating, because
I occasionally miss an interesting "event" that I'm tracking, but it's not
worth the time and effort to spend a bunch of time tracking it down.

The "driver" task just does a "put URL tURL into tMessageHTML" and then
re-triggers itself with a "send "autoCapture to me in tSeconds seconds"
before it processes the tMessageHTML it received.  The task has only one
stack; the mainstack.  I think that means the "autoCapture" message isn't
getting fired in "tSeconds" seconds, or it's getting fired and for some
reason doesn't get processed.

TED
-- 
View this message in context: http://www.nabble.com/How-to-create-a-background-process-tp25616331p25636469.html
Sent from the Revolution - User mailing list archive at Nabble.com.




More information about the use-livecode mailing list