Browse Prior Art Database

Hybrid Interprocess Communications (IPC) Transport Service Utilizing Both a Connection-Based Transport and a Connectionless Transport

IP.com Disclosure Number: IPCOM000123895D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2005-Apr-05
Document File: 1 page(s) / 62K

Publishing Venue

IBM

Related People

Pechacek, J: AUTHOR

Abstract

Disclosed is hybrid network interprocess communications (IPC) transport service which allows an application to leverage the benefits of both connectionless and connection-oriented network services while hiding the details of such network services, including selecting the optimal network service to use for the application and managing network connections.

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

Hybrid Interprocess Communications (IPC) Transport Service Utilizing
Both a Connection-Based Transport and a Connectionless Transport

   Disclosed is hybrid network interprocess communications
(IPC) transport service which allows an application to leverage the
benefits of both connectionless and connection-oriented network
services while hiding the details of such network services, including
selecting the optimal network service to use for the application and
managing network connections.

   The IPC transport service provides an interface for
the application to select one of three types of service for delivery
of each IPC message (each data transfer): "connection required",
connection preferred or "connectionless".  These service types are
described below:
  1.  Connectionless - Messages are delivered using a
      connectionless network protocol (such as UDP in a IP
      network).
  2.  Connection required - Messages are delivered using a
      connection-oriented network protocol (such as TCP in
      an IP network).
  3.  Connection preferred - Messages are delivered using
      connection-oriented network protocol if available
      (i.e., if both endpoint systems have connection
      capability and currently have sufficient resources
      for a connection).  If a connection is not available,
      the message falls back to use the connectionless service.

   To improve performance, a test is performed to determine
whether a connection is available before actual...