R. Balter et al., "Architecture and Implementation of Guide, an Object-Oriented Distributed System", Computing Systems, vol. 4, num. 1, pp. 31-67, 1991.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....via a local area network. The Guide model is based on shared persistent objects. The system offers a strongly typed object oriented programming language [10] and provides system support for object persistency, dis tribution, synchronization and parallel execution (for detailed description see [2] [6] We want to extend the existing scheme for object invocation in Guide to deal with replicated objects. The paper is organized as follows. Section 2 describes three basic techniques for implementing replicated objects. In Section 3, we present a multi class queueing model which reflects the ....

R. Balter et al., "Architecture and Implementation of Guide, an Object-Oriented Distributed System", Computing Systems, vol. 4, num. 1, pp. 31-67, 1991.

....thus providing location, access and execution transparency. The system offers a strongly typed object oriented programming language [Krakowiak et al. 1990] and provides system support for object persistency, distribution, synchronization and parallel execution (for detailed description see [Balter et al. 1991][Decouchant Duda 1990] The first Guide system prototype was implemented on top of Unix. This experience has shown the need for system services which allows the management of nodes, storage volumes, users and groups of users. The second version of Guide system (referred to as Eliott) is being ....

R. Balter et al., "Architecture and Implementation of Guide, an Object-Oriented Distributed System", Computing Systems, vol. 4, num. 1, pp. 31-67, 1991.

....project aims to define an architecture that hides most of the problems inherent to distribution, for storage, execution and resource allocation, thus providing location access and execution transparency. The first implementation of Guide has been carried out on top of the Unix 2 operating system[1]. While supporting several experimental applications such as document editing, intelligent document exchange and distributed diary, it suffers from several limitations, such as the lack of support for fault tolerance. This is particularly important for persistent objects which 1 Guide is a ....

R. Balter, J. Bernadat, D. Decouchant, A. Duda, A. Freyssinet, S. Krakowiak, M. Meysembourg, P. Le Dot, H. Nguyen Van, E. Paire, M .Riveill, C. Roisin, X. Rousset de Pina, R. Scioville and G. Vandome., "Architecture and implementation of Guide, an object-oriented distributed system" In Computing Systems, vol. 4, num. 1, pp. 31-67, 1991.

....is chosen, the activation of a relevant tool is automatically done by the system. Moreover, we provide a specific declarative language called Indra that integrates all these contributions in an homogeneous fashion. Indra has been implemented on top of the Guide object oriented distributed system [2][12] We took advantage of the Guide object model for representing the Indra concepts. A specific compiler was used to translate the definition of the coordinations of the tools and the definition of the Tree Schema into Guide object classes. The late binding of object provided by Guide has ....

Balter R., Bernadat J., Decouchant D., Duda A., Freyssinet A., Krakowiak S., Meysembourg M., Le Dot P., Nguyen Van H., Paire E., Riveill M., Roisin C., Rousset de Pina X., Scioville R., Vandome G., "Architecture and Implementation of Guide, an Object-Oriented Distributed System ", Computing Systems, vol. 4, num. 1, pp. 31-67, 91.

....and the implementation of the multicast protocol. This work has been done in the framework of the Guide project, whose aim is to explore distributed computing structured in terms of objects and basedon a set of workstationsinterconnected via a local area network (for detailed description see [2], 6] 9] The system is intended for cooperative applications such as concurrent document editing and program development. Therefore, object sharing is an important feature of our model; objects are persistent and communication between concurrent activities is done by means of object sharing. ....

Balter et al., "Architecture and Implementation of Guide, an ObjectOriented Distributed System",Computing Systems, vol. 4, num. 1, pp. 31-67, 1991.

....shared memories [27] This paper concerns another model, namely, the shared object model. It is a refinement of the shared memorywhere the unit of replication is an object. Several experimental distributed systemsbased on objects exist: Eden [2] Emerald [9] Clouds [19] Amoeba Orca [24] Guide [5]. They define architectures based on objects which hide most of the problems inherent in distribution thus providing location, access and execution transparency. This work has been done in the framework of the Guide project, whose aim is to explore distributed computing structured in terms of ....

....of a paper presented at the 13th International Conference on Distributed Computing Systems, Pittsburgh (USA) May 1993. y On leave at the MIT Laboratory for Computer Science, Programming Systems Research Group 1 distribution, synchronization and parallel execution (for detailed description see [5][11] Object oriented distributed systems usually exploit parallelism and distribution for speeding up applications or for increasing their availability and reliability. A basic technique for achieving these goal is object replication which can be implemented in several ways. The Echo file ....

R. Balter et al., "Architecture and Implementation of Guide, an ObjectOriented Distributed System",Computing Systems, vol. 4, num. 1, pp. 31-67, 1991.

....problem. Section 3 describes how objects can be represented using significant polyhedral shapes, and how their positions express global relationships and set properties. In section 4, we apply these techniques to a debugging tool running on top of the Guide distributed object oriented system [1]. This visual debugger consists of a set of virtual images giving high visibility of Guide concurrent objectoriented applications. This experimentation illustrates the efficiency of virtual images and shows that the computational and graphical power of standard workstations are efficient enough to ....

....graph is also animatedand objects loaded in memory for execution are popping up. This animation reflects aspects of the virtual memory management in the Guide system. 4 Applying Virtual Images to Distributed Object Oriented Debugging 4. 1 Introduction The overall objective of the Guide project [1] is to build an integrated platform for programming and operating distributed applications. This platform is targeted at application programmers and aims to reduce the overall cost of the development, maintenance and integration of large distributed applications. Guide provides an object oriented ....

R. Balter et al, "Architecture and Implementation of Guide, an ObjectOriented Distributed System",Computing Systems, vol. 4, num. 1, pp. 31-67, 1991.

....to place other timings in context. Remote make reference durable makes the reference to a remote object durable whilst remote make object durable makes a remote object durable. 6. Related Work Many object support systems have been designed. Some examples are Emerald [Black87] Cool [Lea93] Guide [Balter91], Spring [Hamilton93b, Radia93] and Choices [Campbell93] However, these systems have not been designed to run on general purpose operating systems. Network Objects system [Birrell93] offers somewhat similar functionality to Shadows but does not support object mobility, a key feature of our ....

Balter, R. et al, "Architecture and Implementation of Guide, an Object-Oriented Distributed System", Computing Systems, 4 (1), pp. 31-67, April 1991.

....is made) by loading its state and methods from the object store to the volatile store, and associating a server process for receiving RPC invocations. Further, an object provides a convenient unit for concurrency control, storage, replication and migration. Argus [1] Arjuna [2,3] and Guide [4] are just some of many systems designed broadly according to the model outlined above. When constructing an object and action based application, several issues arise concerning object decomposition . How should the application s state be decomposed into objects Which objects should be decomposed ....

Balter, R. et al, "Architecture and Implementation of Guide, an ObjectOriented Distributed System", Computing Systems, 4 (1), pp. 31-67, April 1991.

....ONTOS [Ah91] VERSANT [Ve92] Orion ITASCA, ObjectStore [St88, At90] Some operating systems implement their own versions of objects at the kernel level. These include Argus [Li 87] Cronus [Sc 86] Eden [Al 85] and Clouds [Da 91] Systems such as the Commandos operating system [MaGu89] and Guide [Ba 91] provide extensive language level object support via operating system routines. Memory mapping of objects into applications spaces have been used by Cricket, MONADS and Casper. Cricket [ShZw90] maps the entire object store to the address space of all applications using the store. MONADS [Ro90 uses ....

Balter, R., J. Bernadat, D. Decouchant, et al, "Architecture and Implementation of Guide, an Object Oriented Distributed System," Computing Systems, Vol. 4 No. 1, Winter 1991.

....controlled by the use of atomic actions which have the well known properties of (i) serialisability, ii) failure atomicity, and (iii) permanence of effect. The object and atomic action model provides a natural framework for designing faulttolerant systems with persistent (long lived) objects [1][4][13] 18] 19] Persistent objects not in use are normally resident in a passive state on object stores. A passive object is made active by loading its state and methods from the object store to volatile store and associating a process (a server) for receiving RPCs for method executions. Atomic ....

R. Balter et al, "Architecture and Implementation of Guide, an Object-Oriented Distributed System", Computing Systems, 4(1) April 1991, pp. 31-67.

....enables interpretation of the passive state of an object in an heterogeneous environment. Several prototype object oriented systems have been built, often emphasising different facets of the overall functionality. For example, systems such as Argus [14] Arjuna [11, 23, 29] SOS [28] and Guide [4] have emphasised fault tolerance and distribution aspects, languages such as PSAlgol [3] Galileo [2] and E [25] have contributed to our understanding of persistence as a language feature, while efforts such as [12] have contributed to the understanding of the design of object stores and their ....

Balter, R. et al, "Architecture and Implementation of Guide, an ObjectOriented Distributed System", Computing Systems, 4 (1), pp. 31-67, April 1991.

....accommodate polymorphism rules of languages) and to support persistent shared objects that may be used to build more complex structures by embedding references to external objects within the instance data of an object. This design is based on the following decisions: ffl In a previous prototype [1], each method call was interpreted, i.e. the binding of code and data was checked by the kernel before the actual call. In order to improve performance, interpretation is now only done at first call. ffl Since we only have a 32 bit address space, we reuse space by dynamically mapping clusters in ....

R. Balter, J. Bernadat, D.Decouchant, A.Duda, A. Freyssinet, S. Krakowiak, M. Meysembourg, P. Le Dot, H. Nguyen Van, E. Paire, M. Riveill, C. Roisin, X. Rousset de Pina, R. Scioville, G. Vand ome, "Architecture and implementation of Guide, an object-oriented distributed system", Computing Systems, vol. 4, num. 1, pp. 31-67, Winter 1991.

....of the art with respect to these requirements. Section 4 describes a coordination mechanism called Indra, in terms of its main design principles that fulfill the established requirements. Section 5 reports about the implementation of Indra on top of the Guide object oriented distributed system[2]. Finally, the main results of our experiment as well as the main principles of Indra are summarized in the conclusion. 2 Coordination mechanism requirements As stated in introduction, a coordination mechanism allows software development tools to interact through exchanges of requests and ....

....is chosen, the activation of a relevant tool is automatically done by the system. Moreover, we provide a specific declarative language called Indra that integrates all these contributions in an homogeneous fashion. Indra has been implemented on top of the Guide object oriented distributed system [2][9] The object model of Guide has appeared as very convenient for representing the Indra concepts. Moreover, its execution model has allowed to represent the nodes of the Instantiated Tree by distributed and passive objects, providing a decentralized architecture with acceptable execution ....

Balter R., Bernadat J., Decouchant D., Duda A., Freyssinet A., Krakowiak S., Meysembourg M., Le Dot P., Nguyen Van H., Paire E., Riveill M., Roisin C., Rousset de Pina X., Scioville R., Vand ome G., "Architecture and Implementation of Guide, an Object-Oriented Distributed System", Computing Systems, vol. 4, num. 1, pp. 31-67, 91.

....means they are never garbage collected, and so their target objects are never garbage collected. By this mechanism objects may persist over time even if unreferenced by clients. 5 Related Work Many object support systems have been designed. Some examples are Emerald [Black87] Cool [Lea93] Guide [Balter91], Spring [Hamilton93b, Radia93] and Choices [Campbell93] However, these systems have not been designed to run on general purpose operating systems. Network Objects system [Birrell93] offers somewhat similar functionality to Shadows but does not support object mobility, a key feature of our ....

Balter, R. et al, "Architecture and Implementation of Guide, an Object-Oriented Distributed System", Computing Systems, 4 (1), pp. 31-67, April 1991.

....an invocation is made) by loading its state and methods from the object store to the volatile store, and associating a server process for receiving RPC invocations. Further, an object is a convenient unit for concurrency control, storage, replication and migration. Arjuna [1] Argus [2] and Guide [3] are just some systems designed broadly according to this model. Given this model, replication can be used to improve the availability of objects in the presence of failures. Atomic actions guarantee consistency, while replication allows forward progress for an application. A replication protocol ....

R. Balter et al, "Architecture and Implementation of Guide, an Object-Oriented Distributed System", Computing Systems, 4(1), April 1991, pp. 31-67.

....consists of a universe of objects which are passive and can be distributed. An application is initiated by a process which invokes methods on objects of the universe. Processes communicate with each other by calling methods on shared objects. This model is used by Emerald [3] Orca [4] and Guide [5]. This model is also used by traditional C or Eiffel programmers in a non distributed environment. In fact the blackboard approach may be extended by considering processes to be coarse grained active objects similar to servers in the client server approach. Thus objects are classified into ....

R. Balter, J. Bernadat, D. Decouchant, A. Duda, A. Freyssinet, S. Krakowiak, P. Ledot, M. Meysembourg, H. Nguyen Van, E. Paire, M. Riveill, C. Roisin, X. Rousset de Pina, R. Scioville, G. Vandome, "Architecture and implementation of Guide, an object-oriented distributed system", Computing Systems, vol. 4, num. 1, pp. 31-67, Winter 1991.

No context found.

Balter R., Bernadat J., Decouchant D., Duda A., Freyssinet A., Krakowiak S., Meysembourg M., Le Dot P., Nguyen Van H., Paire E., Riveill M., Roisin C., Rousset de Pina X., Scioville R., Vandome G., "Architecture and Implementation of Guide, an Object-Oriented Distributed System", Computing Systems, Vol.4 (No.1), pp. 31-67, 91.

....object names assignments or comparisons are simple and cheap since they only involve the first field of the names. However, its major drawback is that it requires larger object names that can be space (disk) and time(CPU) consuming. This scheme was used in a first prototype of the Guide system [2] implemented on the Unix system. Objects were named by 32 bit object identifiers and a variable containing an object name was 64 bit length. The support of users that developed large scale applications [5] showed us that 32 bit identifiers were not enough. For the design of the current prototype ....

R. Balter, J. Bernadat, D.Decouchant, A.Duda, A. Freyssinet, S. Krakowiak, M. Meysembourg, P. Le Dot, H. Nguyen Van, E. Paire, M. Riveill, C. Roisin, X. Rousset de Pina, R. Scioville, G. Vand ome, "Architecture and implementation of Guide, an object-oriented distributed system", Computing Systems, vol. 4, num. 1, Winter 1991.

No context found.

Balter91 Balter, R. et al, "Architecture and Implementation of Guide, an Object-Oriented Distributed System," Computing Systems, 4 (1), pp. 3167, April 1991.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC