Wishlist: Command line option to keep file cache contents

[GoogleCodeExporter]

With a current lifetime of 6 days, the chance to update the file cache at the 
second run (e.g., related to issue 190) seems to be small, but it exists. 
Actually, I have run into it _just now_ when - for consistency checks - I ran 
the same search twice, with different output files.

An option to force an "infinity" TTL for cache pages (cdpf.aspx*) - meaning 
that only not-existing files would be retrieved from remote (shouldn't happen 
at all), all other requests served from local file cache - would help avoiding 
such a situation.
This would also be helpful for testing purposes (for example, setting up an 
unmutable test base to run regression tests against).

Cached searches (nearest.aspx*) should not be affected, or controlled by a 
different option - they have another TTL anyway.

[Internally, the setting of this option should be known inside shadowget.rb - I 
haven't found out yet how to accomplish this.]

Original issue reported on code.google.com by Steve8x8 on 10 Jan 2011 at 8:42

[GoogleCodeExporter]

Work in progress.

Original comment by Steve8x8 on 10 Jan 2011 at 10:11

• Changed state: Started

[GoogleCodeExporter]

Will be in 3.16.0

Original comment by Steve8x8 on 2 May 2012 at 1:19

• Changed state: FixAvail

[GoogleCodeExporter]

Although the risk of changing search results or cache descriptions has been 
addressed by the opportunity to output multiple formats in one go, it may be 
nice to keep old cache descriptions (e.g. the ones valid at own find time). The 
-Y option will cause GeoToad to never overwrite a valid cdpf file (by setting 
the age limit to a very long time). This won't affect new fetches.

Original comment by Steve8x8 on 25 May 2012 at 12:18

• Changed state: Fixed