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

216 AppendixD
Migration From PTOP to NetIPC and RPM
Example: Client-Server Application
Example: Client-Server Application
The following sets of programs illustrate the principles for converting a
PTOP application to use NetIPC and RPM.
The sample application is a simple name server, where you run a client
program that creates a server on the node that contains a data file. The
client program sends names to the server. The server looks up the
names in the data file and returns associated information to the client.
The client and server are first presented as PTOP master and slave
programs. Then they are converted to use NetIPC and RPM.
The major points of the conversion are:
• The POPEN call made by the client is replaced by the NetIPC and
RPM calls as detailed in the earlier section “Creating Remote
Processes.” At the beginning of the server, the corresponding NetIPC
and RPM calls are inserted.
• The client’s PWRITE of the name to the server is replaced by an
IPCSEND. The server’s GET and ACCEPT are replaced by an IPCRECV
(actually, one or more IPCRECVs in the RECV procedure).
• The server can ACCEPT or REJECT the client’s PREAD for the name
information, depending on whether the name is found in the data
file. So, in the converted application, the server sends an accept or
reject indication to the client. The ACCEPT is replaced by an
IPCSEND of the name information.
• The accepted PREAD in the client becomes an IPCRECV for the name
information.
• The client’s PCLOSE is replaced by an RPMKILL and IPCSHUTDOWN.