|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
Communication and Synchronization Primitives for Distributed Programs
April 1985 (vol. 11 no. 4)
pp. 396-416
| ASCII Text | x | ||
| N. Natarajan, "Communication and Synchronization Primitives for Distributed Programs," IEEE Transactions on Software Engineering, vol. 11, no. 4, pp. 396-416, April, 1985. | |||
| BibTex | x | ||
| @article{ 10.1109/TSE.1985.232229, author = {N. Natarajan}, title = {Communication and Synchronization Primitives for Distributed Programs}, journal ={IEEE Transactions on Software Engineering}, volume = {11}, number = {4}, issn = {0098-5589}, year = {1985}, pages = {396-416}, doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.1985.232229}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - JOUR JO - IEEE Transactions on Software Engineering TI - Communication and Synchronization Primitives for Distributed Programs IS - 4 SN - 0098-5589 SP396 EP416 EPD - 396-416 A1 - N. Natarajan, PY - 1985 KW - port KW - Atomic action KW - communication failure KW - computing agent KW - distributed operating system KW - distributed piogram KW - distributed system KW - kernel VL - 11 JA - IEEE Transactions on Software Engineering ER - | |||
A distributed program is a collection of several processes which execute concurrently, possibly in different nodes of a distributed system, and which cooperate with each other to realize a common goal. In this paper, we present a design of communication and synchronization primitives for distributed programs. The primitives are designed such that they can be provided by a kernel of a distributed operating system. An important feature of the design is that the configuration of a process, i.e., identities of processes with which the process communicates, is specified separately from the computation performed by the process. This permits easy configuration and reconfiguration of processes. We identify different kinds of communication failures, and provide distinct mechanisms for handling them. The communication primitives are not atomic actions. To enable the construction of atomic actions, two new program components, atomic agent and manager are introduced. These are devoid of policy decisions regarding concurrency control and atomic commitment. We introduce the notion of conflicts relation using which a designer can construct either an optimistic or a pessimistic concurrency control scheme. The design also incorporates primitives for constructing nested atomic actions.
Index Terms:
port, Atomic action, communication failure, computing agent, distributed operating system, distributed piogram, distributed system, kernel
Citation:
N. Natarajan, "Communication and Synchronization Primitives for Distributed Programs," IEEE Transactions on Software Engineering, vol. 11, no. 4, pp. 396-416, April 1985, doi:10.1109/TSE.1985.232229
Usage of this product signifies your acceptance of the Terms of Use.

