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

20040212: Data product Expiration (cont.)

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: 20040212: Data product Expiration (cont.)
  • Date: Thu, 12 Feb 2004 13:39:10 -0700
>From: "Schaffert, Lowell" <address@hidden>
>Organization: Lockheed Martin Corporation
>Keywords: 200402122011.i1CKBbp1029946 LDM queue pqexpire

Lowell,

>Thanks Tom.
>That says to me that if you have a large queue, lets say sized to hold
>10 hours, that you can have data in the queue that could be 10 or more
>hours old. That data will only be removed from the queue when it is
>necessary to insert more items into the queue. Am I correct?

You are correct.  This allows a downstream site to connect to the
server and request data that is as old as the age of the oldest product
in the queue.  Of course, the downstream site can specify how old the
data to be sent is, so it is not necessary that they get all of the old
data.  In fact, the standard configuration for a downstream LDM node is
to request the last one hour of data from the upstream server.

>Thanks,

No worries.

Tom
--