[worldKit-dev] zoom vs file load

Mikel Maron mikel_maron at yahoo.com
Tue Jan 10 03:08:28 PST 2006


I think the most sensible change would be to request tiles only when zooming has stopped. 
There would be a config option to switch between tile loading behavior.

There's not really a request queue as such -- all requests are sent out to the wms as soon as they are required,
and the response time is dependent on that wms.

I added this issue to roundup -- http://www.rockburger.com/roundup/roundup.cgi/worldkit/issue159
Everyone is welcome to dig into any issues of interest. Though at the moment, I can't get involved in coding myself,
but will help as much as possible to navigate through the code and potential solutions to issues.

-Mikel


----- Original Message ----
From: Iain Mott <mott at reverberant.com>
To: Discussion of worldKit use and development <worldkit-dev at lists.brainoff.com>
Sent: Monday, January 09, 2006 10:01:36 PM
Subject: Re: [worldKit-dev] zoom vs file load

to add to that:

I can see the benefit of not flushing 'obsolete' files, in that they
become cached and can viewed again quickly, when for example, the user
zooms out again after zooming in at a given pan position.

As an alternative to flushing, could the files in the queue be
re-ordered such that the ones that are needed at an instantaneous scale,
are loaded first?

iain


On Tue, 2006-01-10 at 08:48 +1100, Iain Mott wrote:
> thanks mikel - this certainly speeds things up. But still, and i haven't
> attempted to look at the mechanism for this, once files are placed in
> the queue for loading, ones that are no longer needed (for a given
> scaling) don't seem to flushed when a new scale has been requested. ie.
> they continue to be loaded even though the scale, at the point in time
> when the files were requested, has been passed. If I understand this
> correctly, could flushing be implemented to make zooming more efficient?
> 
> best, iain
> 
> On Mon, 2006-01-09 at 02:24 -0800, Mikel Maron wrote:
> > Hi Iain
> > 
> > worldKit will, by default, pause when it has 10 or more open requests for images. Having an excessive number of open requests can cause problems; 10 is a very very cautious limit (it should probably be higher).
> > 
> > The config option <maximgload> can be set to a higher number if it improves usability in your map.
> > 
> > Set <showload> to true, and you will be able to monitor this behavior directly.
> > 
> > Mikel
> > 
> > ----- Original Message ----
> > From: Iain Mott <mott at reverberant.com>
> > To: worldkit-dev at lists.brainoff.com
> > Sent: Monday, January 09, 2006 1:23:55 AM
> > Subject: [worldKit-dev] zoom vs file load
> > 
> > hello
> > 
> > This is more a 'user' than 'dev' question, hope that's okay on this
> > list.
> > 
> > When using the zoom controls on a worldkit map with a large data-set, I
> > find that zoom has to wait while non-cached files are being loaded. Is
> > there any way to give precedence to the zoom control?
> > 
> > I'm using firefox on Linux, and sorry I haven't checked if the problem
> > exists in Windows yet. When the map is configured to zoom in on a region
> > using click and drag, the problem is side-stepped to a degree because
> > there is a quick jump to the desired scale - but the problem (or
> > feature) exists here too. The map i'm testing is at:
> > www.reverberant.com/ct 
> > 
> > cheers, Iain
> > 
> > 
> 
> _______________________________________________
> worldkit-dev mailing list
> worldkit-dev at lists.brainoff.com
> http://lists.brainoff.com/listinfo.cgi/worldkit-dev-brainoff.com

_______________________________________________
worldkit-dev mailing list
worldkit-dev at lists.brainoff.com
http://lists.brainoff.com/listinfo.cgi/worldkit-dev-brainoff.com






More information about the worldkit-dev mailing list