Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!clyde!cbosgd!ihnp4!ihlpa!qix
From: qix@ihlpa.ATT.COM (Puckett)
Newsgroups: comp.sys.amiga
Subject: Re: ID-handler - unique-number generator - source and executables
Message-ID: <4273@ihlpa.ATT.COM>
Date: Wed, 17-Jun-87 11:38:03 EDT
Article-I.D.: ihlpa.4273
Posted: Wed Jun 17 11:38:03 1987
Date-Received: Sun, 21-Jun-87 11:17:06 EDT
References: <4228@ihlpa.ATT.COM> <1384@ulowell.cs.ulowell.edu>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 19

In article <1384@ulowell.cs.ulowell.edu>, page@ulowell.UUCP writes:
> qix@ihlpa.ATT.COM (Puckett) wrote:
> >process IDs (being MsgPort addresses) are not necessarily unique on the Amiga
> 
> Of course process IDs are unique.  Actually you probably want Task IDs,
> which the scheduler uses.
> 
I was being sloppy.  What I should have said was that it is possible to
obtain the same process ID twice (a process could go away and another
might *happen* to be allocated with the same MsgPort address).
This would make it slightly unsafe to use Amiga process IDs as mktemp() does,
especially for interprocess communication identifiers (like pipe names)
where a process might create something and then go away.

I do not know about Task IDs.  Does a Task ID ever get reused from
reboot to reboot?  If not, then ID-handler is unnecessary, and Task IDs
will work fine.

			-Ed Puckett.