| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | DLL over a Network |
CM> > Are there one or many pipes? CM> One named pipe, with as many instances as you desire to have multiple clients connected simultaneously. CM> > Who opens the pipe(s)? CM> The server creates and opens the pipes, telling OS/2 how many instances to support. The clients then open the other end to start a connection. You can read all about this in the Control Program Guide and Reference supplied in your Developers' Toolkit, in the section entitled pipes. It's quite thoroughly explained. Even I understand it. (-: CM> > What are they called? How do processes on > different machines, (namely: Client and Server) become > aware of the name of the pipe in use? CM> You design that bit. Either the names are hardwired, or you have some way for the user to configure the pipe name (and the server name for the clients), by using an INI file or a command-line argument, say. > JdeBP < ___ X MegaMail 2.10 #0: --- Maximus/2 2.01wb* Origin: DoNoR/2,Woking UK (0483-725167) (2:440/4) SEEN-BY: 12/2442 54/54 620/243 624/50 632/348 640/820 690/660 711/409 413 430 SEEN-BY: 711/807 808 809 934 942 712/353 623 713/888 800/1 @PATH: 440/4 141/209 865 820 3615/50 229/2 12/2442 711/409 54/54 711/808 809 @PATH: 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™.