NetIPC 3000/XL Programmer's Reference Manual (5958-8600)

Chapter 1 23
NetIPC Fundamentals
Using NetIPC for Interprocess Communication
the process has created. This call socket descriptor is then used in
subsequent NetIPC calls.
Figure 1-2 IPCCREATE (Processes A and B)
2. Naming a Call Socket
Process B associates a name with its call socket by calling IPCNAME (see
Figure 1-3). When a call socket is named, this information is placed in
the socket registry at the local node. The name Process B assigns to its
call socket must also be known to Process A because Process A must
reference it later in its IPCLOOKUP call. (When a socket name is known
to both processes in this way, it is called a well-known name.)
Although call sockets do not have to be named, a process cannot gain
access to the socket of another process if the socket is not named (unless
the address of that socket is known, in which case IPCDEST is used).
The socket must be named and be recorded in the socket registry at the
node of Process B when Process A calls IPCLOOKUP.
Figure 1-3 IPCNAME (Process B)
Call
Socket
Descriptor
Call
Socket
Descriptor
PROCESS A PROCESS B
Call
Socket
Descriptor
Call
Socket
Descriptor
PROCESS A PROCESS B
SOCKET REGISTRY
“NAME”