I am pretty naive, but this looks like it might be the start of supporting something like a mule server.. or ESB, enterprise service bus. has this been done?

I had a couple of thoughts on this.

You could include a callback to provide the dynamic part of the URL (or a function which developers override in a subclass)

Initially my usage would be for a URLLoader that keeps calling until it gets a successful return value, as a a kind of failsafe so that the user doesn’t have to keep requesting data. Although I guess this might just be done via a registered complete handler which cancels once it receives the right data.

Joc

// call initTimer() from constructor
private function initTimer():void
{
timer = new Timer(_refreshInterval);
timer.addEventListener(TimerEvent.TIMER, onTimer);
}

private function stopTimer():void
{
if(timer != null)
{
timer.stop();
}
}

private function startTimer():void
{
stopTimer();

if(_refreshInterval <= 0 || _callIsActive)
{
return;
}

timer.delay = _refreshInterval;

timer.start();
}

I wrote something like this for one of my clients a while ago. I don’t own the rights otherwise i would distribute.

My approach was a bit different. What I did instead of extending loader was that I wrote a LoaderManager class that allowed you to set refresh intervals as well as a slew of other features, per project requirements. anyhow this is how the refresh would look:

LoaderManager.refresh(loaderInstance:Loader, interval:Number, appendTimeStap:Boolean);

I also had a cancelRefresh method, a refreshCount prop and broadcasted an event if the data was different thenn what was previously loaded (part of the managers responsibilities).

I agree with Tom’s suggestion, I like URLPoller.

-erik

Haven’t gotten a chance to play with it yet, but it would be good to have a property to bind for parameters. The reason I wanted this in the first place was for the Twitter client I’m writing. Right now I have timers running to request the user’s timeline every 60 seconds. Currently I have to stop the timer when the request is made and start it back up after the result comes back so I don’t get cached on my second request(the twitter api will cache if you request again before the 60 seconds is up). I’m going to play with it and see if I can add a good way to set the id of the last comment pulled.

Thanks again.

Good catch. I fixed it locally.

Thanks…

mike chambers

mesh@adobe.com