-=> On 05-18-19 05:15, Andrew Leary <=-
-=> spoke to Dale Shipp about Ignore <=-
AL> The serial number may be any eight character hexadecimal number, as
AL> long as it is unique - no two messages from a given system may have
AL> the same serial number
AL> within a three years. The manner in which this serial number is
AL> generated is left to the implementor.
That sure sounds like the MSGID *must* guarantee no dupes.
AL> For normal messaging use, using the Unix time as the base
AL> of your MSGID serial
AL> number is adequate, unless you write messages very quickly, ie: more
AL> than 1 per second. Autoposting of text files to message bases for
AL> such things as online game scores, new file announcements, etc. is usually
AL> where time-based MSGID serial number generation breaks down.
And so folks need to slow that process down. If I were in such a
situation, I would use a batch/cmd file with a time delay between
postings.
DS> I have seen at least one system that had a 16 bit MSGID (rest was 0
DS> filled). That is very inadequate, and repeats can be expected once
DS> 256 messages have been sent.
AL> Such a system would not be compliant with FTS-0009.
I know that , and I made sure that the system was told that.
Dale Shipp
fido_261_1466 (at) verizon (dot) net
(1:261/1466)
... Shipwrecked on Hesperus in Columbia, Maryland. 02:32:31, 19 May 2019
___ Blue Wave/DOS v2.30
--- Maximus/NT 3.01
* Origin: Owl's Anchor (1:261/1466)
|
