Geek asks and answers

Flash / AS3 - is there a limit on the number of simultaneous requests URLLoader.load ()?

All,

I am working on a Flash / AS3 project that calls numerous URLLoader.load () requests.

Do I have to queue them so that at any time there is only one open request? Or is it good to allow multiple open requests?

Is there a limit on the number of open requests?

(I assume that I can manage the consequences in the user interface).

I ran tests locally with 5 concurrent queries and it works fine. But I need to make sure that the application will work in the field, for users with older computers, older browsers, browsers with multiple tabs open, etc.

Many thanks in advance for any advice and insight!

+3
source share
3 answers

I ran into this problem many years ago when I was trying to load a ton of images. They were all local, so I just queued them with the bootloader. The debug hours queue, why the images were empty: S

I'm not sure that the restriction is mentioned anywhere, but I found (if the memory serves) about 30 gave me problems. After that, and I think he will reuse the old connections: so if you have 100 calls to load (), only the last 30 or so are loaded.

Usually I bet about 10 at a time, then load the rest when they finish. There is no real problem with multiple connections - although they will start using processor power, etc.

, - BulkLoader: http://code.google.com/p/bulk-loader/,

+3

, , 5 . , 6 , , , Flash.

- 5 , .

+2

. Google, .

, . URLLoader.load Flex 4.6 AS 3.

. , .

.

timer:Timer = new Timer(5000);
timer.addEventListener(TimerEvent.TIMER, timerHandle);
timer.start();
var loader:URLLoader = new URLLoader(); // and need to add listeners for response

function timerHandle(e:TimerEvent):void {
    loader.load(certainURLRequest);
}

. .

function timerHandle(e:TimerEvent):void {
    loader.load(firstURLRequest); // this request didn't get issued
    loader.load(secondURLRequest); // this request got sent
}

I do not know the insides. This may apply to the ActionLoop ActionScript single-threaded method, where the request will be processed after returning from the callback, and the last one will overwrite the previous one. These are all my guesses.

Hope this helps those coming here.

+1
source

More articles:


All Articles