Browse Prior Art Database

Communication Method Among Asynchronous Processors in a Distributed System

IP.com Disclosure Number: IPCOM000038325D
Original Publication Date: 1987-Jan-01
Included in the Prior Art Database: 2005-Jan-31
Document File: 2 page(s) / 14K

Publishing Venue

IBM

Related People

Ebrahimi, M: AUTHOR [+4]

Abstract

This invention relates to a new use of a service request facility. More particularly, it relates to a method for starting at least one action and communicating with a counterpart executor of said action in a distributed processing system, the executor performing the action locally or remotely. The method steps include (a) invoking a SendRequest operation and responsively creating a message queue associated with the request and action, thereby becoming a client of the request, (b) at the executor, binding a server process to the request, and (c) upon the server process either reading or writing standard operating system input or output, intercepting the reading or writing, and sending a message to the requesting client indicating a remote operation to be performed by the client on behalf of the server.

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

Page 1 of 2

Communication Method Among Asynchronous Processors in a Distributed System

This invention relates to a new use of a service request facility. More particularly, it relates to a method for starting at least one action and communicating with a counterpart executor of said action in a distributed processing system, the executor performing the action locally or remotely. The method steps include
(a) invoking a SendRequest operation and responsively creating a message queue associated with the request and action, thereby becoming a client of the request, (b) at the executor, binding a server process to the request, and (c) upon the server process either reading or writing standard operating system input or output, intercepting the reading or writing, and sending a message to the requesting client indicating a remote operation to be performed by the client on behalf of the server. In this method, if the intercept were an operating system output, then the steps would further include sending output to the requesting client in order to perform the indicated operations, and if the intercept were an operating system input, causing the requesting client to receive the input. Consider a distributed computing system where a process executing at one computer makes requests that are to be handled at another computer.

The method of exploiting such a request facility allows a user (as opposed to a process or program) to communicate with a service program at another computer. The method is especially valuable if the service program assumes a user at the computer where the program runs. This assumption is made, for example, by most personal computer software. A request may be started from within a program by means of a SendRequest function. A process that issues SendRequest is called the "client" of that request; the process that handles the request is called the "server". A process becomes a server by invoking the ReceiveRequest function. The request establishes a channel of communication between client and server through which they may communicate by sending and receiving messages (invoking Send and Receive functions). The same process can be a client for a number of requests. A process can be a server for exactly one request (and one client) at a time. Each partner in the request has a queue on which it receives messages from the other partner. The invention exploits the fact that one process can start many requests. One process at each user's computer, acting as a surrogate for the user, is the client for all requests that are made directly by the user. The term "action" is used for a request started by the user, and the surrogate process is termed the "action monitor". The action monitor communicates with the user, who has the option of: - starting...