This time a question, a bit off-topic.
As you know, I'm implementing syslog-sign. And I wondering "when" to
send a SignatureBlock.
The RFC doesn't mentions it (it shouldn't). But maybe somebody a an
opinion about it. A SignatureBlock is always send between 2 normal
messages, using UDP.
In normal cases, it really doesn't matter when it is send, typical,
all messages are received, mostly "in-order". That is typical,
although UDP doesn't guaranty it.
Messages get lost when the network is "to busy". Or when a cable is
temporally unplugged (for a short time).
So, if two messages are send directly after each other
a) the make the network more busy. (So it losses the 2nd),
b) both fall of the lose plug (usually)
The code can try to send messages to increase the probability that all
are received or that "most important one" is received.
My questions is, how to to so.
To simplify the matter, in the examples below each hash is sent only
once. S<n> is the SignatureBlock containing the hash of M<n>.
Each dot represents some (real) time, but not the same about every time.
Option 1: M1 S1 ... M2 S2 ...
Option 2: M1 ... S1 M2 ...S2 M3 ...
Option 3: M1 ... M2 S1 ...M3 S2 ...
Option 4: M1 .. S1 .. M2 .. S2 ..
Option 4 seams nice, to balance the load. But is complex (iff
possible) to implement.
Options 1-3, and variants are more real. I have selected 1 for now, as
it is easy to debug:-) Before I used opt 2, but I'm not sure whether
is actually "better".
Please share you idea's THANKS
--
ALbert Mietus
Send prive mail to: [EMAIL PROTECTED]
Send business mail to: [EMAIL PROTECTED]
Don't send spam mail!
