Persistent shared object support in the Guide system: evaluation & related work

  • Authors:
  • Daniel Hagimont;P.-Y. Chevalier;A. Freyssinet;S. Krakowiak;S. Lacourte;J. Mossière;X. Rousset de Pina

  • Affiliations:
  • University of British Columbia, Department of Computer Science, 2366 MainMall, Vancouver, B.C. Canada V6T 1Z4 and Bull-IMAG/Systèmes, 2 av. de Vignate, 38610 Gières - France;European Computer-Industry Research Center (ECRC), Arabellastrasse 17, D-81925 Munich, Germany and Bull-IMAG/Systèmes, 2 av. de Vignate, 38610 Gières - France;Bull-IMAG/Systèmes, 2 av. de Vignate, 38610 Gières - France;Bull-IMAG/Systèmes, 2 av. de Vignate, 38610 Gières - France;Bull-IMAG/Systèmes, 2 av. de Vignate, 38610 Gières - France;Bull-IMAG/Systèmes, 2 av. de Vignate, 38610 Gières - France;Bull-IMAG/Systèmes, 2 av. de Vignate, 38610 Gières - France

  • Venue:
  • OOPSLA '94 Proceedings of the ninth annual conference on Object-oriented programming systems, language, and applications
  • Year:
  • 1994

Quantified Score

Hi-index 0.00

Visualization

Abstract

The purpose of the Guide project is to explore the use of shared objects for communication in a distributed system, especially for applications that require cooperative work. Since 1986, two prototypes have been implemented respectively on top of Unix (Guide-1) and Mach 3.0 (Guide-2). They have been used for the development of distributed cooperative applications, allowing us to validate or reject many design choices in the system.This paper gathers the lessons learned from our experience and compares the basic design choices with those in other distributed object-oriented systems. The lessons may be summarized as follows. This system layer must provide a generic interface for the support of several object-oriented languages. It must manage fine grained objects and enforce protection between objects and processes. These requirements can be achieved with an acceptable trade-off between protection and efficiency.