Browse Prior Art Database

Single-Process Interoperable Client/Server Executable

IP.com Disclosure Number: IPCOM000123404D
Original Publication Date: 1998-Oct-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 1 page(s) / 42K

Publishing Venue

IBM

Related People

Hlava, A: AUTHOR

Abstract

Disclosed is the use of a single process that can play the role of either a distributed client or server:a single-process, interoperable combined client/server This combined client/server is offered as an alternative where the customer does not need the flexibility of fully distributed clients and servers, but may gradually grow into that environment.

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

Single-Process Interoperable Client/Server Executable

   Disclosed is the use of a single process that can play the
role of either a distributed client or server:a single-process,
interoperable combined client/server This combined client/server is
offered as an alternative where the customer does not need the
flexibility of fully distributed clients and servers, but may
gradually grow into that environment.

The combined client/server process is designed as follows:
  o  Link the existing client and server code together into one
     executable.
  o  Have separate "listen threads" for both the client and the
     server such that they can receive external requests as if
     they were separate processes.
  o  Design the communications layer in the application to
     support both over-the-wire distributed requests and local
     direct calls.

   The support for both remote and local function calls in
this model is provided in the low-level communication system code.
This is designed as follows:
  o  The client and server namespace entries contain both the
     system on which the process resides, and the process ID
     (PID) of that process.  This is part of the "binding
     information" stored when the entry is created/updated.
  o  When the communication system code has obtained the binding
     information for a request, it performs a check and takes
     one of two paths:
     -  If the system name and PID matc...