views:

275

answers:

2

Silverlight's MultiScaleImage appears to only allow two simultaneous connections to request tiles, irrespective of subdomain or browser connection limits. This makes panning or zooming the a DeepZoom image really slow.

How can this connection limit be overriden?

Silverlight doesn't appear to support the usual app.config/maxConnections setting used by .Net apps.

EDIT: I've been able to verify the number of simultaneous connections using Fiddler. The old version of our application (written in ASP.net) uses all available connections in IE, but the same tiles rendered in the MultiScaleImage control in Silverlight are only requested two at a time.

A: 

I thought this was a browser limitation, not a Silverlight limitation.

BPerreault
No, it's separate from the browser limitation as the ASP.net application is using all 10 available connections on my machine to fetch tiles, but Silverlight is only using two.
X-Cubed
I will be watching for the answer then.
BPerreault
I found this: http://stackoverflow.com/questions/229011/aynchronous-web-server-calls-in-silverlight-and-maximum-http-connections
BPerreault
@X-Cubed: What do you mean by the ASP.NET application using all 10 connections? Connections to what? from what?
AnthonyWJones
@AnthonyWJones - From the web application on the client to the tile servers.We currently render the tiles in an ASP.net application, and it makes use of all 10 available connections at a time (I modified my registry so that IE had a max connection limit of 10). But when the same tile are rendered in Silverlight using the MultiScaleImage control, only two tiles are requested simultaneously.
X-Cubed
A: 

Silverlight will use the underlying HTTP stack provided by the browser so that it can benefit from a common cookie and cache management. It would seem logical then that the underlying stack's connection limit would apply to Silverlight.

A simple way to check would be to host the SL app in Firefox which has a more generous default limit (and is more easily tweaked via about:config). Does it make use of more connections? If so then the reason why you seeing only two is because WinINET (the HTTP stack used by IE) is limited to 2 connections by default.

AnthonyWJones