Send In Time
andre at andregarzia.com
Fri Jan 28 13:39:55 EST 2011
not parallel processing but wishful programming, you use a send in
time and hope that no other command block the engine long enough for
its scheduling thing to go bananas.
since you control everything, when you program with send in time, you
keep your code out of blocking situations so that the engine can work
On Fri, Jan 28, 2011 at 4:33 PM, Bob Sneidar <bobs at twft.com> wrote:
> So correct me if I am wrong, but send in time is not really a parallel process is it? It just means that given a send in time of 5 seconds, that after 5 seconds the engine will wait for the first idle message and then execute, and while it's executing nothing else can occur till it's finished?
> Or do I have that wrong?
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://www.andregarzia.com All We Do Is Code.
More information about the Use-livecode