By Topic

CPI-C: An API for distributed applications

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $33
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

7 Author(s)
W. S. Arnette ; IBM Networking Software Division, P.O. Box 12195, Research Triangle Park, North Carolina 27709, USA ; A. D. Kshemkalyani ; W. B. Riley ; J. P. Sanders
more authors

Distributed applications have fostered the standardization of application programming interfaces for the underlying communication services. Three popular communication models—remote procedure calls, messaging and queuing, and conversations—support distributed applications across different networking protocols and physical media. Access to the conversational services of Advanced Program-to-Program Communication and Open Systems Interconnection-Distributed Transaction Processing is provided by the Common Programming Interface for Communications (CPI-C), a standard, easy-to-use interface for communication programming. This paper introduces the basic concepts of CPI-C, describes the conversation services available to programs, and presents examples of CPI-C programming.

Note: The Institute of Electrical and Electronics Engineers, Incorporated is distributing this Article with permission of the International Business Machines Corporation (IBM) who is the exclusive owner. The recipient of this Article may not assign, sublicense, lease, rent or otherwise transfer, reproduce, prepare derivative works, publicly display or perform, or distribute the Article.  

Published in:

IBM Systems Journal  (Volume:34 ,  Issue: 3 )