Path: utzoo!attcan!uunet!ginosko!usc!polyslo!vlsi3b15!vax1.cc.lehigh.edu!lusgr
From: lusgr@vax1.cc.lehigh.edu (STEVE ROSEMAN)
Newsgroups: news.software.anu-news
Subject: Re: How about making Message-ID:'s more unique?
Message-ID: <8849@vax1.cc.lehigh.edu>
Date: 30 Aug 89 09:43:32 GMT
References: <10147@kuhub.cc.ukans.edu>
Organization: Lehigh University
Lines: 23

In article <10147@kuhub.cc.ukans.edu>, SLOANE@kuhub.cc.ukans.edu (Bob Sloane) writes:
> .....I
> would like to suggest that the Message-ID: be a little more complicated than
> just <number@site>, perhaps something like <number.pid@site>, where pid is the
> Process ID of the process creating the article.  This would tend to make it
> VERY unlikely that a job with a duplicate ID would be generated, even if the
> NEWS.GROUPS file was restored from a previous time.
> +-------------------+-------------------------------------+------------------+
> |  Bob Sloane        \Internet: SLOANE@KUHUB.CC.UKANS.EDU/Anything I said is |
> |  Computer Center    \ BITNET: SLOANE@UKANVAX.BITNET   / my opinion, not my |
> |  University of Kansas\  AT&T: (913) 864-0444         /  employer's.        |
> +-----------------------+-----------------------------+----------------------+
-- 

I would suggest a Message-ID: which includes a date/time stamp.
Besides being unique, it gives some real indication of the message's
originating time. 

-------------------------------------------------------------------------
Steve Roseman
Lehigh University Computing Center
LUSGR@VAX1.CC.Lehigh.EDU