Browse Prior Art Database

Network Independent Client/Server Programming Interface

IP.com Disclosure Number: IPCOM000116810D
Original Publication Date: 1995-Nov-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 8 page(s) / 220K

Publishing Venue

IBM

Related People

Davis, RA: AUTHOR [+2]

Abstract

Within a client / server environment it is desirable to have one defined programming interface regardless of the network protocol currently in use. Currently each network protocol (Netbios, TCP/IP, Named Pipe) has it's own programming interface. The Network Independent Client/Server Programming Interface defines an architecture by which one programming interface is exposed to application programmers and support for various protocols can be installed as needed. In addition, a given application program can communicate using more than one protocol at any given time.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 27% of the total text.

Network Independent Client/Server Programming Interface

      Within a client / server environment it is desirable to have
one defined programming interface regardless of the network protocol
currently in use.  Currently each network protocol (Netbios, TCP/IP,
Named Pipe) has it's own programming interface.  The Network
Independent Client/Server Programming Interface defines an
architecture by which one programming interface is exposed to
application programmers and support for various protocols can be
installed as needed.  In addition, a given application program can
communicate using more than one protocol at any given time.

      Within the computer industry it is becoming very important to
be able to communicate between computers.  Being able to support
network communications via different protocols adds complexity to
application program and a confusion factor for the application user.
The Network Independent Client Server Programming Interface
simplifies the programming interface and at the same time simplifies
network support for the application programmer, and in addition
allows any complying network module to be plugged in and existing
applications support it immediately.

      The Network Independent Client Server Programming Interface
provides a mechanism by which software applications support network
communications via one programming interface.  Support for various
network protocols is added at a network support level.  This allows
an application to communicate utilizing network protocols as
available without having to update their programs.  One network
support module is required to support any application using the
Network Independent Client Server Programming Interface.

      The Network Independent Client Server Programming Interface
consists of a dynamic link library (DLL), containing the network
independent support functions used by application programs, and
network support DLLs for each network protocol to be supported.
Following is a list of network independent support functions
available for the application programmer;
  NETACCEPT (HNET)*

Completes connection to client - NetAccept completes the connection
to a client request acknowledged by the NetListen call.  After this
call is issued, the connection is ready for data transfer using
NetSend, NetReceive, or NetTransaction.
  NETCALL (NETWORK, ROUTE, REQUEST)

Perform a single, point-to-point transaction with a closed network
resource

      NetCall performs one complete point-to-point transaction with a
closed network resource.  This call is equivalent to calling NetOpen,
NetConnect, NetSend, NetReceive, and NetClose to perform a single
transaction with the network resource.

Note: To use the default network, specify "" for Network.  If a
specific network must be used, specify the network name for Network
(e.g., for named pipe specify "Named Pipe").
  NETCALLCONNECTION (HNET, REQUEST)

Perform a network transaction on an open connection

...