Distributed programming in GARF

Garbinato, Benoît; Guerraoui, Rachid; Mazouni, K.

doi:10.1007/bfb0017543

Cited by 20 publications

(16 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We faced the mismatch when experimenting the use of our first prototype (named GARF [15]) through a replicated distributed diary manager application. RoughIy speaking, each member of our group had a (replicated) diary used to store the list of meetings to which the member participates (the application is detailed in [15]). …”

Section: Introductionmentioning

confidence: 99%

System support for object groups

Guerraoui

Felber

Garbinato

et al. 1998

Proceedings of the 13th ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications

Self Cite

View full text Add to dashboard Cite

This paper draws several observations from our experiences in building support for object groups. These observations actually go beyond our experiences and may apply to many other developments of object based distributed systems.Our first experience aimed at building support for Smalltalk object replication using the Isis process group toolkit.It was quite easy to achieve group transparency but we were confronted with a strong mismatch between the rigidity of the process group model and the flexible nature of object interactions.Consequently, we decided to build our own object oriented protocol framework, specifically dedicated to support object groups (instead of using a process group toolkit).We built our framework in such a way that basic distributed protocols, such as failure detection and multicasts, are considered as first class entities, directly accessible to the programmers. To achieve flexible and dynamic protocol composition, we had to go beyond inheritance and objectify distributed algorithms.Our second experience consisted in building a CORBA service aimed at managing group of objects written on different languages and running on different platforms. This experience revealed a mismatch between the asynchrony of group protocols and the synchrony of standard CORBA interaction mechanisms, which limited the portability of our CORBA object group service. We restricted the impact of this mismatch by encapsulating asynchrony issues inside a specific messaging sub-service.We dissect the cost of object group transparency in our various implementations, and we point out the recurrent sources of overheads, namely message indirection, marshaling/unmarshaling and strong consistency.

show abstract

Section: Introductionmentioning

confidence: 99%

System support for object groups

Guerraoui

Felber

Garbinato

et al. 1998

Proceedings of the 13th ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications

Self Cite

View full text Add to dashboard Cite

show abstract

“…Adaptive and reflective middleware [42,43] can inspect its internal representation at runtime and reconfigure its state and behavior by providing a set of meta-level interface or object for base-level implementation that handles the real service execution and operations. Open ORB [44] provides both structural reflection and behavioral reflection.…”

Section: Middleware Techniquesmentioning

confidence: 99%

A context-aware reflective middleware framework for distributed real-time and embedded systems

Liu¹,

Cheng²

2011

Journal of Systems and Software

View full text Add to dashboard Cite

Software has become crucial to develop vehicle systems. Future unmanned intelligent vehicle safety systems will increasingly rely on situational contexts collected at runtime through temporally built ad-hoc and dynamic networks for vehicle-to-vehicle and vehicle-to-roadside communications and dynamic adaptation to the contexts to improve vehicle safety and reduce traffic congestion. Context-aware reflective middleware, which can measure real-time contexts and accordingly reconfigure the behavior of supported applications, is an important technique to enhance the affordability, flexibility, and adaptability of the future vehicle safety systems. However, the long reconfiguration time of existing context-aware reflective middleware cannot satisfy the stringent real-time requirement of the vehicle systems and thus limits its adoption. In this paper, we present MARCHES, a context-aware reflective middleware framework, which improves the reconfiguration efficiency for engineering adaptive real-time vehicle applications in dynamic environments. Different from traditional single component-chain based middleware, MARCHES supports an original structure of multiple component chains to reduce local behavior change time. Further, according to the new structure, a novel synchronization protocol using active messages is proposed to reduce distributed behavior synchronization time. Experimental results show that the reconfiguration time of MARCHES is reduced from seconds (s) to hundreds of microseconds (μs). Evaluations demonstrate that MARCHES is also robust and scalable and generates small memory footprint, which makes it suitable for supporting real-time vehicle applications.

show abstract

“…GARF [20,21] lies between the system layer (which supplies the distribution mechanisms) and the application layer. Its basic purpose consists of wrapping the distribution primitives and supplying a uniform and abstract interface to them.…”

Section: Related Workmentioning

confidence: 99%

Remote method invocation as a first-class citizen

Cazzola

2003

Distributed Computing

View full text Add to dashboard Cite

The classical remote method invocation (RMI) mechanism adopted by several object-based middleware is 'black-box' in nature, and the RMI functionality, i.e., the RMI interaction policy and its configuration, is hard-coded into the application. This RMI nature hinders software development and reuse, forcing the programmer to focus on communication details often marginal to the application being developed.Extending the RMI behavior with extra functionality is also a very difficult job, because added code must be scattered among the entities involved in communications.This situation could be improved by developing the system in several separate layers, confining communications and related matters to specific layers. As demonstrated by recent work on reflective middleware, reflection represents a powerful tool for realizing such a separation and therefore overcoming the problems referred to above. Such an approach improves the separation of concerns between the communication-related algorithms and the functional aspects of an application. However, communications and all related concerns are not managed as a single unit that is separate from the rest of the application, which makes their reuse, extension, and management difficult. As a consequence, communications concerns continue to be scattered across the meta-program, communication mechanisms continue to be black-box in nature, and there is only limited opportunity to adjust communication policies through configuration interfaces.In this paper we examine the issues raised above, and propose a reflective approach specially designed to open up the Java RMI mechanism. Our proposal consists of a new reflective model, called multi-channel reification, that reflects on and reifies communication channels, i.e., it renders communication channels first-class citizens. This model is designed both for developing new communication mechanisms and for extending the behavior of communication mechanisms provided by the underlying system. Our approach is embodied in a framework called mChaRM, which is described in detail in this paper.

show abstract

Distributed programming in GARF

Cited by 20 publications

References 13 publications

System support for object groups

System support for object groups

A context-aware reflective middleware framework for distributed real-time and embedded systems

Remote method invocation as a first-class citizen

Contact Info

Product

Resources

About