Process Communication Based on Input Specifications
Authors:
Open Access
- 1 July 1981
- journal article
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Programming Languages and Systems
- Vol. 3 (3) , 224-250
Abstract
Input tools, originally introduced as a language model for interactive systems and based on high-level, input-driven objects, have been developed into a model for communicating parallel processes, called the input tool process model (ITP). In this model every process contains an input rule, comparable to the right-hand side of a production rule. This rule specifies in an expression the patterns and sources of input it exPects and where the input is to be handled. The reception of the input triggers action inside the too! process. As part of the action, messages may be sent to other processes, with destination specified to a varying degree of identification. A potential candidate for a message is any tool process with the correct type of message slot. Because sending tool processes do not have to specify completely the identity of receiving tool processes, and vice versa, ITP provides a fully dynamic communication model. Most communication aspects of other recently developed models are contained in this model. Synchronization of processes is accomplished implicitly by the input specification; explicit synchro- nizatiQn constructs such as monitors and guarded regions can therefore be easily simulated. The ITP constructs provide a general concept for interprocess communication. Its application areas range from interaction via process control to operating systems. From a programming point of view, the language constructs offered are not in any way dependent on whether processes run on single or multiple processors.Keywords
This publication has 13 references indexed in Scilit:
- An alternative to the communication primitives in ADAACM SIGPLAN Notices, 1980
- Comments on ADA process communicationACM SIGPLAN Notices, 1980
- Communication Port: A Language Concept for Concurrent ProgrammingIEEE Transactions on Software Engineering, 1980
- Rationale for the design of the Ada programming languageACM SIGPLAN Notices, 1979
- High level programming for distributed computingCommunications of the ACM, 1979
- Distributed processesCommunications of the ACM, 1978
- Specification and Implementation of Mutual ExclusionIEEE Transactions on Software Engineering, 1978
- Communicating sequential processesCommunications of the ACM, 1978
- Guarded commands, nondeterminacy and formal derivation of programsCommunications of the ACM, 1975
- The UNIX time-sharing systemCommunications of the ACM, 1974