Hello Maurice.

15 Feb 05 09:01, you wrote to me:

 RT>> Thereafter one needs to make it "meaningfull" :-))

 MK> I agree wholeheartedly.  If it is indeed a desirable variable then it
 MK> should be a useful variable across the board and not some hodge-podge
 MK> local solution.  Make it a real network standard or just drop the damn
 MK> thing altogether.

Hmmm ... , I figure they are useful, and can be mayhap made better use of than 
they currently are, so I'm not to keen on dropping them (msgid's) too quickly. 
:-)

 RT>> That leaves the question of how does one generate/create/format a
 RT> RT>> "meaningfull" base ID, and still leave enough
"space to add
 RT>> "uniqueness"

 MK> So far the base ID generated before the msg creation loop, based on a
 MK> date/time call, seems to generate the most useable result.  Two more
 MK> characters (10 instead of just eight) viewed as a hex string with a
 MK> predetermed set of hex digit(s) as unique variables produces the most
 MK> useable ID string here at Kumalockasun.  So far the best I can come up
 MK> with is, yydddmmssx, where yy=two digit year (100 years), ddd=day of
 MK> year, mm=minutes, ss=seconds, and x=actual message number incremented
 MK> in the message creation loop which would then limit pkt sizes to a
 MK> total of 16 messages.  If more then 16 messages then the entire cycle
 MK> is repeated and the ss part incremented by one if the first pass took
 MK> less then a second, which is entirely possible, actually probable here
 MK> for a whole sh*tload of pkts.  :-)

Seems a reasonable solution ...

Russell

--- GoldED+/LNX 1.1.4.7