Hey Russell!

Feb 15 16:56 05, Russell Tiedt wrote to Maurice Kinal:

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

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

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

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

Life is good,
Maurice

--- Msged/LNX 6.1.2