Hello Maurice!

 MK> It won't matter since two or more systems will have two or more unique
 MK> addresses..

 MK>   MSGID: 1:153/7001.0 01234567
 MK>   MSGID: 1:153/7001.1 01234567

OH!  Ok, if dupe-checking takes into consideration the "address"  
part along with the "serialno" part, then uniqueness is pretty  
good as it stands.

I thought the concern was that some dupe-check implementations  
only use the "serialno" part.

 MK> ..As for random collisions there isn't any guarentee that
 MK> either of the above two systems won't create a collision
 MK> within three years no matter how remote that possibility
 MK> is..

True. There could very well be a collision created on the same  
system given enough time.

 MK> whereas the serial number created by the number of seconds
 MK> since 1970|1900 should NEVER create a collision within it's
 MK> lifetime, 2106 in my particular case..

Good point. That guarantees uniqueness. You win.

 MK> ..Adding more characters doesn't add meaning or additional
 MK> functionality to it.

BUT.. you must agree that the likely hood of two rando numbers  
colliding given that any of the 8 chars in the serialno part can  
be [a-z][A-Z][0-9] at 62^8, is pretty unlikely.

Even a serial number based on an incremental 8 char string with  
[a-z][A-Z][0-9] could work too.

I'm amazed how long the services of TinyURL have relied on 8- 
char uniqueness.  As far as I can tell they only use the  
lowercase letters + the numbers:

https://tinyurl.com/ydpdc3td
https://tinyurl.com/ydt9y4os

 ..the service as been operating for a l-o-n-g time.


And, now that we've totally bored the vast number of ASIAN_LINK  
listeners, we should probably move to something less technical.

--
  ../|ug

--- OpenXP 5.0.49