TIP: Click on subject to list as thread! ANSI
echo: os2prog
to: Peter Fitzsimmons
from: Peter Schuller
date: 1997-03-16 11:25:14
subject: Re: Message pipes

> DosCreatePipe() is for anonymous pipes -- a completely different monster,  
 > from the unix world,  ususally used for redirection and piping the output 
 > from one program to another.

 > DosCreateNPipe() is used to create named pipes, message mode or byte mode.

 >    > And I want it
 >  PS> to be unnamed, since 
 >  PS> several processes will call the same routine.

 > More than one process can use the same pipe name to connect to the server 
 > process(es).

Yeah, I read about that. But each process will be separate, I will simply 
startx several instances of on EXE. Prefarably without any multi-process 
implementation. Each process shouldn't have to know if it's "alone" or if 
there are 123 other instances of itself. But as I understand it, a named pipe 
can only exist as one pipe, serverclient. But can however allow multiple 
clients access the same pipe, but not multiple servers. That's the problem. I 
could do a "super-server" that takes care of all the pipe:ing,
but it would 
take to much CPU, 3 times as much.

Is it at all possbile to achive the possibility to create multiple instances 
of one pipe that is 100% separate when the clients/servers are concerned?
I wanna save as much CPU as possible. And to modify names of the pipes both in 
the server/client would hog some extra CPU.

Thank you very much!

/ Peter Schuller   [TeamOS/2]   petere.schuller{at}noreva.se


--- AdeptXBBS v1.08a26 (VC) (Registered)
* Origin: Gamma Epsilon 24h/day +46-(0)18-367781 (2:206/139)
SEEN-BY: 50/99 54/99 270/101 620/243 625/155 160 711/401 413 430 934 712/311
SEEN-BY: 712/407 505 506 517 623 624 704 713/317 800/1
@PATH: 206/100 205/625 270/101 712/624 711/934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.