« Return to Thread: what actually happens when sending a message out of a repeat loop?

Re: what actually happens when sending a message out of a repeat loop?

by Jan Schenkel :: Rate this Message:

Reply to Author | View in Thread

--- Eric Chatonet <eric.chatonet@...>
wrote:

> Bonjour Richard et Sivakatirswami,
>
> Le 23 juin 08 à 18:45, Richard Gaskin a écrit :
>
> > Also, in polling timers I've found it very helpful
> to first check  
> > to see if a message is already queued before
> queueing it again, e.g.:
> >
> >  on DoPolling
> >    DoSomething
> >    if "DoPolling" is not in the pendingMessages
> then
> >      send "DoPolling" to me in 200 millisecs
> >    end if
> >  end DoPolling
>
> I agree so much that I think that the engine itself
> could ignore sent  
> messages that are already in the pending messages
> except when the  
> delay is zero.
>
> Best regards from Paris,
> Eric Chatonet.
>

Hi Eric et al,

While I can see the advantages of Revolution
'collapsing' requests, I'm not sure this should be the
default behaviour - and definitely not if there are
parameters involved, as the sequence then becomes very
important.
Plus, what about timers that run every minute?

Jan Schenkel.

Quartam Reports & PDF Library for Revolution
<http://www.quartam.com>

=====
"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)


     
_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

 « Return to Thread: what actually happens when sending a message out of a repeat loop?

LightInTheBox - Buy quality products at wholesale price!