home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!csus.edu!netcom.com!netcomsv!terapin!paulk
- From: paulk@terapin.com (Paul Kienitz)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: IPC and shared memory
- References: <1993Jan4.220638.12229@jato.jpl.nasa.gov>
- Message-ID: <paulk.33x4@terapin.com>
- Date: 5 Jan 93 20:31:39 PST
- Organization: BBS
- Lines: 14
-
- > Declare the Signal Semaphore structure itself or a pointer to it in
- > your main program's data area and then restore that area in any sub
- > tasks/pro-cesses that wish to gain access to the semaphore.
-
- This only works if all processes that access the semaphore all run
- off the same SegList. This means that you have to launch the program
- once, and yet have it spawn multiple processes running the same code,
- internally, in response to different users. If you're going to do
- that, you might as well implement all the good stuff in a single
- server process which doesn't need any internal semaphoring anyway.
-
- Using a named semaphore makes things way simpler, if you really do
- want to use concurrent processes and not a centralized server
- bureaucrat-process.
-