Hey All!   
      
   A new tearline with three hex id fields delimited by '.', where the   
   first field is the wireless user's name, the second the echo's id and   
   the third the message's id.  For this echo the id will remain the same   
   even if it is crossposted to a different echo and could be used to check   
   if a message was indeed crossposted.  The user's id should be consistent   
   no matter where that user posts.  The last field is the only field that   
   is unique but is possible to duplicate on a multiuser system if two or   
   more users create a message at the same time which is why the user id is   
   employed in case of that event and the two or more messages in any given   
   echobase should still be unique.  A bit of overkill but it should   
   address a more active multiuser system's concern about uniqueness.  I've   
   seen it happen although not for roughly a decade now.   
      
   What do you think?  Is it a keeper?   
      
   Life is good,   
   Maurice   
      
   --- WeBeBashing 8ec52452.f86639ed.38a4b237   
    * Origin: Pointy Stick Society (1:261/38.9)