Hey Russell!

Feb 15 09:01 05, Maurice Kinal wrote to Russell Tiedt:

 MK> useable ID string here at Kumalockasun.  So far the best I can come 
 MK> up with is, yydddmmssx, where yy=two digit year (100 years), ddd=day 
 MK> of year, mm=minutes, ss=seconds, and x=actual message number 
 MK> incremented in the message creation loop which would then limit pkt 
 MK> sizes to a total of 16 messages.  If more then 16 messages then the 
 MK> entire cycle is repeated and the ss part incremented by one if the 
 MK> first pass took less then a second, which is entirely possible, 
 MK> actually probable here for a whole sh*tload of pkts.  :-)

One other thing I forgot to mention about the above is the 8.3 DOS
limitation for pkt names and that can be resolved from the above by using
yymmddss.pkt, or whatever suitable already needed and carried variables, to
generate a unique pkt name.  The only thing one would have to worry about
is not to create a dupe pkt name within the time it is storing pkt's to
when those pkt's are transported to wherever since pkt names shouldn't, and
probably aren't, used for dupe checking any particular messages.  With this
addition I believe that takes care of compatibility if the lowest common
denominator - the most crippled OS, DOS - is taken into account across the
board.  Near as I can figure, with a message size limitation within the
message creation loop, the above ideology ought to work no matter which OS
or language employed is used.  It should work unless someone else spots
something I've forgotten to take into account.  That happens.  Sigh.

Life is good,
Maurice

--- Msged/LNX 6.1.2