The Unidata Local Data Manager (LDM) system includes network client and server programs designed for event-driven data distribution, and is the fundamental component of the Unidata Internet Data Distribution (IDD) system.
Currently, a synchronous, round-trip NULLPROC message is used to flush the connection every time the end of the product-queue is hit or every 30 seconds, whichever comes first.
Replace the use of this NULLPROC with the sending of an empty (i.e., "nil") data-product using the "message passing" capability of the RPC layer (i.e., non-NULL reply decoder but a zero timeout value). If the MD5 signature of the nil data-product is the same as the last successfully-transmitted data-product, then this should be backward-compatible.
Doing this will use the network more efficiently because the upstream LDM will not wait for a reply from the downstream LDM.
Currently, a synchronous, round-trip NULLPROC message is used to flush the connection every time the end of the product-queue is hit or every 30 seconds, whichever comes first.
Replace the use of this NULLPROC with the sending of an empty (i.e., "nil") data-product using the "message passing" capability of the RPC layer (i.e., non-NULL reply decoder but a zero timeout value). If the MD5 signature of the nil data-product is the same as the last successfully-transmitted data-product, then this should be backward-compatible.
Doing this will use the network more efficiently because the upstream LDM will not wait for a reply from the downstream LDM.