experimental change: render stale map data tiles before downloading fresh data - should give a more responsive appearance of data
also increase cache expiry time to 15 mins
This commit is contained in:
parent
c4990d31bd
commit
8270812406
@ -11,7 +11,7 @@ window.DataCache = function() {
|
||||
// entries would grow indefinitely. an hour seems reasonable from experience with the data, so 55 mins max cache time
|
||||
// this.REQUEST_CACHE_MAX_AGE = 55*60; // maximum cache age. entries are deleted from the cache after this time
|
||||
//UPDATE: this timestampMs parameter doesn't work, so reduced max age to limit RAM usage
|
||||
this.REQUEST_CACHE_MAX_AGE = 5*60; // maximum cache age. entries are deleted from the cache after this time
|
||||
this.REQUEST_CACHE_MAX_AGE = 15*60; // maximum cache age. entries are deleted from the cache after this time
|
||||
|
||||
if (L.Browser.mobile) {
|
||||
// on mobile devices, smaller cache size
|
||||
|
@ -247,7 +247,15 @@ window.MapDataRequest.prototype.refresh = function() {
|
||||
this.cachedTileCount += 1;
|
||||
} else {
|
||||
|
||||
// no fresh data - queue a request
|
||||
// no fresh data
|
||||
|
||||
// render the cached stale data, if we have it. this ensures *something* appears quickly when possible
|
||||
var old_data = this.cache && this.cache.get(tile_id);
|
||||
if (old_data) {
|
||||
this.render.processTileData (old_data);
|
||||
}
|
||||
|
||||
// queue a request
|
||||
var boundsParams = generateBoundsParams(
|
||||
tile_id,
|
||||
latSouth,
|
||||
|
Loading…
x
Reference in New Issue
Block a user