scispace - formally typeset
Journal ArticleDOI

Architectural support for quality of service for CORBA objects

J. Zinky, +2 more
- 01 Jan 1997 - 
- Vol. 3, Iss: 1, pp 55-73
Reads0
Chats0
TLDR
The architecture, Quality of Service for CORBA Objects (QuO), is described, which is developed to overcome limitations and integrate their solution by providing QoS abstractions to CORBA objects.
Abstract
CORBA is a commercial standard for distributed object computing which shows great promise in the development of distributed programs. Its interface description language (IDL) enables objects to be developed independently of the underlying programming language, operating system, or computer architecture on which they will execute. While this is sufficient in many environments, programs deployed in a wide-area distributed system encounter conditions which are much more hostile and varying than those operating in a single address space or within a single local area network. In this paper we discuss four major problems we have observed in our developing and deploying wide-area distributed object applications and middleware. First, most programs are developed ignoring the variable wide area conditions. Second, when application programmers do try to handle these conditions, they have great difficulty because these harsh conditions are different from those of the local objects they are used to dealing with. Third, IDL hides information about the tradeoffs any implementation of an object must make. Fourth, there is presently no way to systematically reuse current technology components which deal with these conditions, so code sharing becomes impractical. In this paper we also describe our architecture, Quality of Service for CORBA Objects (QuO), which we have developed to overcome these limitations and integrate their solution by providing QoS abstractions to CORBA objects. First, it makes these conditions first class entities and integrates knowledge of them over time, space, and source. Second, it reduces their variance by masking. Third, it exposes key design decisions of an object's implementation and how it will be used. Fourth, it supports reuse of various architectural components and automatically generates others. © 1997 John Wiley & Sons, Inc.

read more

Citations
More filters
Proceedings ArticleDOI

AQuA: an adaptive architecture that provides dependable distributed objects

TL;DR: The AQuA architecture allows distributed applications to request a desired level of availability using the Quality Objects (QuO) framework and includes a dependability manager that attempts to meet requested availability levels by configuring the system in response to outside requests and changes in system resources due to faults.
Journal ArticleDOI

End-to-end quality of service for high-end applications

TL;DR: The prototype GARA implementation builds on differentiated services mechanisms to enable the coordinated management of two distinct flow types-foreground media flows and background bulk transfers-as well as the co-reservation of networks, CPUs, and storage systems.
Proceedings Article

Quality of services specification in distributed object systems design

TL;DR: It is shown how QML can be used to capture QoS properties as part of designs, and UML, the de-facto standard object-oriented modeling language, is extended to support the concepts of QML.
Journal ArticleDOI

Smart Generation and Transmission With Coherent, Real-Time Data

TL;DR: Major challenges facing electrical generation and transmission today that availability of coherent, real-time measurements can help address are described and key factors for these power applications that influence how the delivery system should be planned, implemented, and managed are described.
Journal ArticleDOI

QoS-aware middleware for ubiquitous and heterogeneous environments

TL;DR: Four key aspects of a QoS-aware middleware system are presented: QoS specification to allow description of application behavior and QoS parameters;QoS translation and compilation to translate specified application behavior into candidate application configurations for different resource conditions; QoS setup to appropriately select and instantiate a particular configuration; and finally, QoS adaptation to adapt to runtime resource fluctuations.
References
More filters
Journal ArticleDOI

RSVP: a new resource ReSerVation Protocol

TL;DR: The resource reservation protocol (RSVP) as discussed by the authors is a receiver-oriented simplex protocol that provides receiver-initiated reservations to accommodate heterogeneity among receivers as well as dynamic membership changes.
Book

The art of metaobject protocol

TL;DR: A new approach to programming language design is presented, which resolves fundamental tensions between elegance and efficiency, and a metaobject protocol is presented that gives users the ability to incrementally modify the language's behavior and implementation.
Book

The Art of the Metaobject Protocol

TL;DR: In this article, the authors present a new approach to programming language design, which resolves fundamental tensions between elegance and efficiency, called metaobject protocols, which are interfaces to the lanaguage that give users the ability to incrementally modify the language's behavior and implementation, as well as to write programs within the language.
Journal ArticleDOI

RSVP: a new resource reservation protocol

TL;DR: A resource reservation protocol (RSVP), a flexible and scalable receiver-oriented simplex protocol, that provides receiver-initiated reservations to accommodate heterogeneity among receivers as well as dynamic membership changes and supports a dynamic and robust multipoint-to-multipoint communication model.
Book ChapterDOI

A Note on Distributed Computing

TL;DR: In this paper, the authors look at a number of distributed systems that have attempted to paper over the distinction between local and remote objects, and show that such systems fail to support basic requirements of robustness and reliability.
Related Papers (5)