I think you have to be careful here. I think the limitation on number of open connections is in the browser. If you have large resources or slow servers and you raise that limit, you could saturate the browsers connections.

On 2007-06-12, at 00:41 EDT, Qrowd Support wrote:

Hi Henry,

For all my LZX projects, including Cooqy, I always set LzLoadQueue.maxOpen = 10; as the first line in my canvas.oninit() method...it makes that much of a difference in media loading performance, I always hardcode this setting, overriding the default value of 2.

I saw the warnings in the source code you refer to, but they didn't prove to be accurate...my programs have run without issues using a higher setting. I remember during my testing that extremely high settings like 50 did cause problems, though, as I seem to recall. But a value of 10 has worked well for me in all my LZX applications, especially for Cooqy which loads lots of eBay images.

Robert Yeager
Founder, Qrowd
http://www.qrowd.com/blog
http://www.qrowd.com <http://www.qrowd.com>


Henry Minsky wrote:
There is code in LzLoadQueue which carefully tries to maintain no more than two open network connections (data , media, snippets, whatever). The reasoning that was explained to me back in the Flash 5 days was that more than two open connections would cause load requests
to silently fail in Internet Explorer.

I recall trying to verify this in Flash 6, and wasn't convinced it was still an issue. I'm looking at this code now because there's a bug which has been reported (LPP-4115) which is causing the lzLoadQueue to believe that it has run out of connections. It seems stupid to restrict our requests to two at a time if it's not necessary, so I'm going to try some experiments to figure out if this throttling is needed at all anymore. I haven't seen any documentation that says that requests will be lost if multiple outstanding
requests are issued in SWF.



--
Henry Minsky
Software Architect
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>


Reply via email to