I've been implementing Seadragon (as part of the ACT), but have recently found some users complaining of slow speeds whilst using it - I thought this odd because the whole idea of Seadragon and DeepZoom is streaming images as they're required rather than loading one huge image in one request.
I've done a bit of testing (using Firebug) on both our web pages and the ASP.net ACT Sample website Seadragon control, and have found that when the control is opened on screen, the browser decides to load all the tile images at once (even the tiles which aren't at the default zoom level).
Has anyone else experienced this and does anyone know why it does it/if there's a fix? The fact it happens on the ACT sample site has left me tearing my hair out because I know that it's not just my implementation of the control that's causing problems.
View Complete Post