NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Actually, I should have said, "accept" instead of "allow". A caveat is that the client needs to be ready to receive when you send the product, or they'll miss it (unless you have some way that they can request that you resend it) Another is that the filename of the product you send has to be the same as what you want the header to be seen as on the client end. You also have to come up with scripts to send the products when they become available (perhaps the scripts could be launched from pqact when your LDM has received and saved the product to a file that you can resend.) The upside is that you control EXACTLY who gets sent what and when since you have to manually specify it all. I'd strongly caution against multiple LDM's running on a machine since besides the non-trivial technical issues, the performance is likely to be terrible unless the products are few and tiny due to cache being spread thin across all of the queues, plus their overhead. -----Original Message----- [mailto:owner-ldm-users@xxxxxxxxxxxxxxxx]On Behalf Of David Wojtowicz Sent: Saturday, November 22, 2003 6:00 PM You could push the product with ldmsend like WSI does with their products rather than have the clients pull the products. (clients need to add an allow line to their ldmd.conf) ------------------------------------------------------- David Wojtowicz, Sr Research Programmer / Systems Admin Department of Atmospheric Sciences Computer Services University of Illinois at Urbana-Champaign (217) 333-8390 davidw@xxxxxxxx -------------------------------------------------------
ldm-users
archives: