Browse Prior Art Database

Local Inter-Process Communication using Berkeley Software Distribution Sockets for OS/2

IP.com Disclosure Number: IPCOM000106746D
Original Publication Date: 1993-Dec-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 2 page(s) / 54K

Publishing Venue

IBM

Related People

Cheng, C: AUTHOR [+3]

Abstract

Communication between peer processes performing remote and/or local communication, running on IBM's OS/2*, require writing to different Application Programming Interfaces (APIs) with completely different interface semantics. One goal of the Local Inter-process Communication (LIPC) is to provide the ability of the programmer to utilize a single API to perform both remote PC to PC and local Process to Process communication using the same semantics. This removes the need to learn, understand, and write code to multiple API's when the requirement arises to perform both types of communication.

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

Local Inter-Process Communication using Berkeley Software Distribution Sockets for OS/2

      Communication  between  peer  processes performing remote
and/or local communication, running on IBM's OS/2*,  require  writing
to  different Application  Programming  Interfaces  (APIs) with
completely different interface semantics.   One goal of the Local
Inter-process Communication (LIPC) is to provide the ability of the
programmer to utilize a single  API  to  perform  both  remote  PC
to PC and local Process to Process communication using the same
semantics.  This removes the need to learn, understand, and  write
code  to  multiple  API's  when  the requirement arises to perform
both types of communication.

      The above problem  can  be solved by routing data over a LAN
network protocol to/from the same node.  Although this resolves the
problem, it is at the cost of performance, executing extra network
protocol layers.

      A local domain sockets interface is implemented based on the
API and semantics provided by the  Berkeley Software Distributions
(BSD) 4.3 socket APIs.  This solution will provide a subset of the
4.3 BSD API calls which relate more directly with establishing a data
path and method of data transfer.  Provide resource control, data
management and perform communication without routing data over a
network.  Local IPC support along with socket access over other
network protocols in OS/2 provides a single API that:

...