On Sat, 6 Jan 2007 05:59:55 +0100
J.D. Bakker [EMAIL PROTECTED] wrote:
typedef struct {
short header_len; // This field is always present, and always first
short data_len;// This field is always present, and always second
[ header contents, including header version, type, etc.
Hi Leif and all,
- I would want a timestamp in there somewhere. It might be derived
from block_no, but why not make it explicit ?
I do not see what it would be good for. Why do you want the clock
from the master while there is another one in the slave?
Surely I could add this, but there
Hi Joe and all,
I agree that a timestamp will be useful. For what I am
thinking about, very high precision and high accuracy are
not required. JT65 wants to know the UTC of a data block to
within a second or so. (Relative timing among successive
blocks is of course maintained by the
Leif and all,
Would you agree on milliseconds since midnight? From JDB I
learned that a double with seconds since Unix epoch
would be a bad idea since conversion may be difficult on
non-PC platforms. (It is the internal time format within
Linrad however)
Yes, milliseconds since UTC
A general point: in virtually all communications protocols the
(descriptive) header comes before the data block, since the receiver
usually needs to decode the header to be sure what to do with the
data. This also makes it possible to vary the length of the data
block, if desired (for
