Re: Updating Aggregations in TDS
- To: John Caron <address@hidden>
- Subject: Re: Updating Aggregations in TDS
- From: Roy Mendelssohn <address@hidden>
- Date: Thu, 30 Oct 2008 08:50:34 -0700
I am glad we understand how recheckEvery works. It is consistent with
what we were experiencing.
basically you want to do the recheck in the background, and then
accept whatever is there when a request comes in? Or you want to
detect whenever the directory changes?
Because other things, such as web page displays, need to be updated
when data is added, we already have a system where we know when data
have been added to a dataset. What we would like to do is at that
point force a recheck for that dataset, and hopefully only for that
dataset, rather than the entire catalog. If we can do that, we
probably will turn off the recheckEvery because we know every dataset
will be up to date.
Does this makes sense? If need be, we can write a script in Java to
do the above, if we can get advice on the best way to do this.
"The contents of this message do not reflect any position of the U.S.
Government or NOAA."
Supervisory Operations Research Analyst
Environmental Research Division
Southwest Fisheries Science Center
1352 Lighthouse Avenue
Pacific Grove, CA 93950-2097
e-mail: address@hidden (Note new e-mail address)
"Old age and treachery will overcome youth and skill."
"From those who have been given much, much will be expected"
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.