Barbara Liskov
Abstract
Argus—a programming language and system developed to support the implementation and execution of distributed programs—provides mechanisms that help programmers cope with the special problems that arise in distributed programs, such as network partitions and crashes of remote nodes.
- 1 Andrews, G.R., and Olsson, R.A. The evolution of the SR language. Distrib. Comput. 1, 2 (Apr. 1986). Also Tech. Rep. 85-22, Univ. of Arizona, Tucson, Ariz., Oct. 1985.Google Scholar
Cross Ref
- 2 Davies, C.T. Data processing spheres of control. IBM Syst. J. 12, 2 (1978), 179-198.Google Scholar
- 3 Gray, J.N. Notes on data base operating systems. In Lecture Notes in Computer Science. G. Goos and J. Hartmanis, Springer-Verlag, New York, 1978, pp. 393-481. Google Scholar
- 4 Gray, J.N., Lorie, R.A., Putzolu, G.F., and Traiger, I.L. Granularity of locks and degrees of consistency in a shared data base. In Modeling in Data Base Management Systems. G.M. Nijssen, Ed. North Holland, Am~terdam, 1976.Google Scholar
- 5 Greif, I., Seliger, R., and Weihl, W. A case study of CE?;: A distributed collaborative editing system implemented in Argus. Programming Methodology Group Memo 55. MIT Laboratory for Computer Science, Cambridge, Mass. Apr. 1987. To be published in IEEE Transactions on Software Engineering. Google ScholarDigital Library
- 6 Hayes, B. Computer recreations: On the ups and downs of hailstone numbers. Scientif. Amer. 250, 1 (Jan. 1984).Google ScholarCross Ref
- 7 Herlihy, M., and Wing, J. Avalon: Language support for reliable distributed systems. In Proceedings of the 17th International Symposium on Fault-Tolerant Computing, (Pittsburgh, Pa., July). IEEE, New York, 1987.Google Scholar
- 8 Ichbiah, J., et al. Rationale for the design of the Ada programming language. SIGPLAN Not. 14, 6 {June 1979). Google ScholarDigital Library
- 9 Lampson, B.W., and Sturgis, H.E. Crash recovery in a distributed data storage system. Tech. Rep. Xerox Research Center, Pa}o Alto, Calif., 1979.Google Scholar
- 10 Liskov B. Overview of the Argus language and system. Programming Methodology Group Memo 40. M.I.T. Laboratory for Computer Science, Cambridge, Mass., Feb. 1984.Google Scholar
- 11 Liskov B., et al. Argus reference manual. Tech. Rep. MZ{T/LCS/TR- 400. M.I.T. Laboratory for Computer Science, Cambridge, Mass., 1987. Google ScholarDigital Library
- 12 Liskov, B., Curtis, D., Johnson, P., and Scheifler, R. implementation of Argus. In Proceedings of the 11th Symposium on Operating Systems Principles {Austin, Texas, Nov.}. ACM, New York, 1987. Google ScholarDigital Library
- 13 Liskov B., and Guttag, J. Iteration abstraction. In Abstraction and Specification in Program Development. MIT Press, Cambridge, Mass., and McGraw Hill, New York, 1986. Google ScholarDigital Library
- 14 Liskov B., and Scheifler, R.W. Guardians and actions: Linguistic support for robust, distributed programs. ACM Trans. Prog. Lang. Syst. 5, 3 (July 1983). 381-404. Google ScholarDigital Library
- 15 Liskov B., Snyder, A., Atkinson, R.R., and Schaffert, J.C. Abstraction mechanisms in CLU. Commun. ACM 20, 8 (Aug. 1977), 564-576. Google ScholarDigital Library
- 16 Mitchell, J.G., Maybury, W., and Sweet, R. Mesa language manual version 5.0. Tech. Rep. GSL-79-3. Xerox Research Center, Palo Alto, Calif., 1979.Google Scholar
- 17 Moss, J.E.B. Nested transactions: An approach to reliable distributed computing. MIT Press, Cambridge, Mass., 1985. Google ScholarDigital Library
- 18 Mueller, E., Moore, J., and Popek, G. A nested transaction mechanism for LOCUS. In Proceedings of the 9th ACM Symposium on Operating Systems Principles (Bretton Woods, N.H., Oct.}. AClvl, New York, 1983. Google ScholarDigital Library
- 19 Spector, A.Z., et al. Camelot: A distributed transaction facility for Mach and the lnternet--An interim report. Tech. Rep. CMU-CS-87-129. Dept. of Computer Science, Carnegie Mellon University, Pittsburgh, Pa., 1987.Google Scholar
- 20 Weihl, W., and Liskov, B. Implementation of resilient, atomic data types. ACM Trans. Prog. Lang. Syst. 7, 2 {Apr. 1985}, 244-269. Google ScholarDigital Library
Index Terms
- Distributed programming in Argus
Recommendations
Comparing novice programing environments for use in secondary education: App Inventor for Android vs. Alice
Coding is part of logical thinking and is one of the basic skills which are known as '21st-century skills'. Coding acquisition is necessary as it is used in a wide range of occupations. However, computer programing is difficult to learn and programing ...
Type-theoretic foundations for concurrent object-oriented programing
A number of attempts have been made to obtain type systems for object-oriented programming. The view that lies common is “object-oriented programming = λ-calculus + record.” Based on an analogous view “concurrent object-oriented programming = concurrent ...
Reviews
Peter B. Danzig
Liskov uses program excerpts to illustrate how the Argus system exploits its programming language to create resilient, easily expressed, distributed programs. The paper walks the reader through the design of a distributed banking database, and serves as an excellent introduction to the author's Argus work. It is written for a general audience and includes references to many Argus papers and related work. The paper describes the tools of resilient programming: atomic actions, nested actions, locking, and recovery. It tersely illustrates nested atomic actions and lock propagation and warns that it has not solved the deadlock detection and avoidance problems inherent to locking. The two principal abstractions of Argus are guardians and actions. “An Argus guardian is a special kind of abstract object whose purpose is to encapsulate a resource or resources. It permits its resource to be accessed by means of special procedures, called handlers.” An Argus action is essentially a nested atomic transaction. Argus is unique because it provides atomic actions within a programming language. It is more general than database transaction processing systems because it operates on general objects within a programming language; it is not an interface to an underlying database. The paper is well written and shorter than previously published descriptions of Argus. It describes an important area of operating system research (see the companion papers in this issue for an overview of other current operating system research projects).
Access critical reviews of Computing literature here
Become a reviewer for Computing Reviews.
Comments