ActionQueue execution delay.

[andyhatch]

I'm using the LoaderQueue class now in an app that has a lot of images
loading at init. This load, even though it is in the queue, seems to
be competing with other simultaneous loads on the site. I was
thinking that putting a 200ms delay between requests in the queue
could decrease competition for bandwidth and make for a smoother
load. This would be in addition to limiting the thread count in the
ActionQueue.

For now I'm extending ActionQueue class to put a delay between
executed actions. Is this a feature that could be added to the
ActionQueue class or is there a better way of doing this?

[David Knape]

The browser limits the number of simultaneous requests, but if you set
the thread count on the action queue to 1, other simultaneous requests
should still get through.

As for adding a delay, there is already a delay in the ActionQueue
class method 'run'. It is currently hard-coded for 10ms, but this
could easily be turned into a configurable parameter or patched to add
a longer delay if that is what you desire.

Let me know if things are behaving strangely.

Thanks.

-dk

--
David Knape
Programmer / Consultant
http://bumpslide.com/

[andyhatch]

I noticed the delay in the 'run' method, but that only affects the
start of the ActionQueue, correct. I was trying to put a delay after
the end of one action and before the start of the next.

I ended up extending Action and overriding the 'execute' method as
follows:

override public function execute() : void
{
if(_delay > 0) // delay is a protected var that defaults to 0
Delegate.callLater(_delay, action);
else
super.execute();
}
}


I couldn't extend LoaderQueue because the _queue and _actions
variables are private, so I created a new LoaderQueue class for my own
use and substituted Action with my own extension in the 'load'
method. Would be nice if LoaderQueue was extensible with protected
instead of private vars.

On Aug 28, 7:00 pm, David Knape <tkd...@gmail.com> wrote:
> The browser limits the number of simultaneous requests, but if you set
> the thread count on the action queue to 1, other simultaneous requests
> should still get through.
>
> As for adding a delay, there is already a delay in the ActionQueue
> class method 'run'.  It is currently hard-coded for 10ms, but this
> could easily be turned into a configurable parameter or patched to add
> a longer delay if that is what you desire.
>
> Let me know if things are behaving strangely.
>
> Thanks.
>
> -dk
>
> --
> David Knape

> Programmer / Consultanthttp://bumpslide.com/

[David Knape]

Actually, I believe the run method is called each time, but I should
double-check that. Your point about making those variables protected
is quite valid. I'll look into that.

Thanks for the feedback. I'm glad you're able to put this code to use.

-dk

--
David Knape
Programmer / Consultant
http://bumpslide.com/

[andyhatch]

Saw r191. Thanks!

On Sep 2, 5:57 pm, David Knape <tkd...@gmail.com> wrote:
> Actually, I believe the run method is called each time, but I should
> double-check that.  Your point about making those variables protected
> is quite valid.  I'll look into that.
>
> Thanks for the feedback.  I'm glad you're able to put this code to use.
>
> -dk
>
> --
> David Knape

> Programmer / Consultanthttp://bumpslide.com/

[andyhatch]

Also, can you let me know what the verdict is on the run method?