How to handle a "wait for file" situation

[Mark Smith]

Craig, you're quite right, and so is Jaque, but in this case, the  
script is running as a cgi on a server, so has it's own exclusive  
copy of the engine running it - so nothing else would be getting held  
up. In another case, though, you might use "wait 1 second with  
messages", which pauses the current handler for the specified time,  
while allowing other stuff to happen....I think there's a good  
tutorial somewhere on the various ways you use these different ways  
of waiting and sending messages and so-on, but I can't remember  
where...was it Dar Scott?

Best,

Mark

On 9 Jun 2009, at 16:14, DunbarX at aol.com wrote:

> It has been beaten (mercilessly) into me by Ms. Gay that this does  
> just the
> opposite; "wait" makes everythiing wait.
>
> Craig Newman
>
>
> In a message dated 6/9/09 10:28:16 AM, lists at futilism.com writes:
>
>
>> Richard, it might help with cpu efficiency to use a different wait in
>> the loop, polling every second, let's say:
>>
>> repeat
>>     add 1 to count
>>     if there is a file xxx then exit repeat
>>     wait 1 second -- I'm assuming that this form of wait just  
>> idles the
>> engine
>>     if count >= 18 then exit repeat -- ie.there's a problem
>> end repeat
>>
>>
>
>
>
>
> **************
> Download the AOL Classifieds Toolbar for local deals at your
> fingertips.
> (http://toolbar.aol.com/aolclassifieds/download.html? 
> ncid=emlcntusdown00000004)
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution