Unclear data source caching

anushani / atlasmapper

Automatically exported from code.google.com/p/atlasmapper

0 stars 0 forks source link

Unclear data source caching #23

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

The rules that apply to caching of the capabilities documents for datasources 
is unclear. Notes on this topic should be added to the text on the datasources 
page.

It is unclear when the clear capabilities button needs to be pressed.

Original issue reported on code.google.com by eric.law...@gmail.com on 14 Mar 2012 at 4:59

GoogleCodeExporter commented 9 years ago

Better caching supported will be available on the next release (1.2-rc2).

Original comment by lafond.g...@gmail.com on 17 May 2012 at 6:37

Changed state: Started

GoogleCodeExporter commented 9 years ago

Better caching algorithm is now available in 1.2.
This enhancement is waiting for disk caching (instead of memory caching) before 
modifying the text for the data sources.

Original comment by lafond.g...@gmail.com on 31 May 2012 at 1:01

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

(Correction on the comment of 26th nov 2012)
Disk caching is now implemented (version 1.3) but some issue has to be 
addressed first; what happen when a corrupted document is downloaded and the 
one in cache is okay, do the application use the old one without noticing the 
user? The user should decide if the error can be ignored or if the generation 
should be aborted. Also, the update process of the document should be done 
automatically, using something like a cron (once a day?) instead of at every 
generation. That should speed things considerably.

Original comment by lafond.g...@gmail.com on 12 Jul 2013 at 5:14

GoogleCodeExporter commented 9 years ago

Version 1.4
The caching do not use an arbitrary "timeout" logic any more. On every data 
source generation, the user can choose to re-download the capabilities document 
(if applicable) and / or the MEST metadatas (if applicable). It is a lot more 
strait forward, but the data source / client description should still be 
revised to explain how, why and what happen after pressing the "Rebuild" button.

Original comment by lafond.g...@gmail.com on 12 Jul 2013 at 5:21

GoogleCodeExporter commented 9 years ago

The caching process was dated in version 1.4.x and is a clearer process. Data 
sources have their own cache that are updated manually. Clients are then built 
from these sources (from their caches).

Original comment by eric.law...@gmail.com on 2 Sep 2013 at 6:06

Changed state: Done