# Time out from multiple loaders

**URL:** <https://forum.kirupa.com/t/time-out-from-multiple-loaders/305440>\
**Category:** flash\
**Created:** [February 25, 2010, 12:31pm UTC](https://forum.kirupa.com/t/time-out-from-multiple-loaders/305440 "2010-02-25T12:31:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shaedo](https://avatars.discourse-cdn.com/v4/letter/s/e19b73/32.png) [@Shaedo](https://forum.kirupa.com/u/Shaedo)\
**Post date:** [February 25, 2010, 12:31pm UTC](https://forum.kirupa.com/t/time-out-from-multiple-loaders/305440/1 "2010-02-25T12:31:11Z")

</div>

Picking up on something **wvxvw** said recently in another thread:

> [@wvxvw;2538920](#):
>
> you shouldn’t start several loading operations concurrently, you should wait for the first loading to complete and then start another loading, otherwise you are risking to get “request timed out”

Had me wondering. I recently changed things around in several of my scripts when I found that running multiple loaders would speed my overall time spent loading by a significant amount (often halving the loading time).

So I was curious for some more information and opinions on the matter. Multiple loaders running at the same time: good, bad, ugly ?

Does it make a difference if I am using the

```auto
var g:NetConnection=new NetConnection();/*create netConnection for getting page names*/
var r:Responder=new Responder(SN,OE);
g.connect("http://www.XXXXXXXX/amfphp/gateway.php");
g.connect("amfphp/gateway.php");
g.call('Page.PN',r);

```

method ?