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

Re: Homegrown LDM pickup . . .

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: Re: Homegrown LDM pickup . . .
  • Date: 30 Oct 2003 11:29:17 -0700
Stonie,

I do all work through the libldm.a routines.

That is, I allocate a MD5 context and update the signature as the
4-5 Kbyte chunks arrive from the dish (much more efficient to do this
for 10+Megabyte satellite images than waiting to
use pqinsert program after a full product arrives)

Then, when the product is complete, finalize the MD5, and fill in the
product structure and insert into the LDM queue using:
status = pq_insert(pq, &prod);

where pq is the product queue opened at the beginning, and prod is a
data structure containing the data, signature, sequence number,
produjct identifier, timestamp and product size.

Steve




On Tue, 2003-10-28 at 19:33, Stonie R. Cooper wrote:
> Steve,
> 
> Finally getting around to updating our plugin from the 5.2.x series to 6.0.x 
> series.  I had attempted just compiling our code against 6.0.3, and it would 
> run for awhile, then the queue insertion would get in a race condition.
> 
> Thus my question . . . for your own homegrown NOAAPort inserter . . . do you 
> use pqinsert, pqing, or something completely different as your starting 
> point?
> 
> Thanks!  We currently use pqinsert . . . but I noticed the code has not 
> changed at all from 5.2.x to 6.0.x . . . and thus was wondering if it is 
> really supported under 6.0.x.