[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #GYQ-484919]: cache configuration

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #GYQ-484919]: cache configuration
  • Date: Fri, 23 Jun 2017 16:39:17 -0600
Hi Fan,

Great, I'm glad it's working! This was a weird corner case. FileCache looks at 
a dataset's last-modified time in order to detect if an entry is stale and 
needs to be refreshed. Checking that is easy if the dataset is local; the OS 
can tell you. But for OPeNDAP (and probably other remote formats), that info 
isn't readily accessible. So we just assume those remote datasets never change. 
And so the cache can grow stale.

Cheers,
Christian

Ticket Details
===================
Ticket ID: GYQ-484919
Department: Support THREDDS
Priority: High
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.