Thread View: comp.os.os2.programmer
2 messages
2 total messages
Started by Skelter
Sat, 23 Jan 1993 20:55
How to communicate between two programs
Author: Skelter
Date: Sat, 23 Jan 1993 20:55
Date: Sat, 23 Jan 1993 20:55
5 lines
678 bytes
678 bytes
How would you allow two programs to actively communicate with each other like you were going to write a program that was a game server and another that was a client. -s
Re: How to communicate between two programs
Author: Jim Kunzman
Date: Wed, 27 Jan 1993 04:01
Date: Wed, 27 Jan 1993 04:01
22 lines
1420 bytes
1420 bytes
According to css0860@sigma.tamu.edu (Skelter): >How would you allow two programs to actively communicate with >each other like you were going to write a program that was a game >server and another that was a client. > >-s > You have several choices with OS/2, but I would probably use named pipes. For an excellent book on implementing same, see _Client/Server Programming with OS/2 2.0_ by Robert Orfali and Dan Harkey, VNR Computer Library Press. I wrote a client/server app under OS/2 1.1 a few years ago which used named pipes and it was fairly painless (even without the above book). You could also used shared memory and semaphores or message queues, but named pipes are really easy and you can even use them across a Netware or LAN Manager network. Now that portable Netware is available for some UNIXen, you can even run named pipes to UNIX servers, e.g. AIX! Good luck with your C/S application. -- Jim Kunzman at Teltronics/TCT <jim@tct.uucp>, <uunet!pdn!tct!jim> ----- Microsoft Windows NT - The Emperor's New Clothes
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads