-
1. Re: parallel loaders fail to fire some Event.COMPLETE
kennethkawamoto2 Oct 19, 2011 5:49 AM (in response to eprevot123)There is a limit for the concurrent download connections imposed by the browser. For example IE is 2 by default. However issuing 4 load requests at the same time should be absolutely fine. Try BulkLoader https://github.com/arthur-debert/BulkLoader to see if it handles your downloads any better.
--
Kenneth Kawamoto
-
2. Re: parallel loaders fail to fire some Event.COMPLETE
eprevot123 Oct 20, 2011 6:09 AM (in response to kennethkawamoto2)I saw Firefox and Chrome limit the number of concurrent connections to 6 so it should not be a problem.
I tried BulkLoader and it works but it creates just 2 concurrent connections for each host domain.
I could do the same and limit the number of concurrent loads to 2 per domain but I think the total download would be slower, so I'm still trying to have more concurrent downloads.
I see many topics on several forums about the Event.complete no being fired but no solution for me.
Is this a known problem ? should I stop trying to have more than 2 concurrent downloads ?
-
3. Re: parallel loaders fail to fire some Event.COMPLETE
kennethkawamoto2 Oct 20, 2011 6:36 AM (in response to eprevot123)You can set the max number of connection for BulkLoader with maxConnectionsPerHost property. So why don't you set it to 6 or higher and test to see if the problem actually lies in the number of the connections or something else.
--
Kenneth Kawamoto
-
4. Re: parallel loaders fail to fire some Event.COMPLETE
eprevot123 Oct 20, 2011 7:41 AM (in response to kennethkawamoto2)I think I finally understand what is the problem :
I added an anonymous function as eventListener for the complete event, and use weak reference.
according to this post it seems to be the problem.
The weird thing is I do the same for progress events but I receive all of them.



