Middleware for Communications 2004
DOI: 10.1002/0470862084.ch6
|View full text |Cite
|
Sign up to set email alerts
|

QoS‐Enabled Middleware

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
48
0
1

Year Published

2004
2004
2014
2014

Publication Types

Select...
5
2
1

Relationship

5
3

Authors

Journals

citations
Cited by 44 publications
(49 citation statements)
references
References 0 publications
0
48
0
1
Order By: Relevance
“…In conjunction with colleagues at Washington University [8], we have developed the Component-Integrated ACE ORB (CIAO) [9] CCM implementation. CIAO extends our previous work on The ACE ORB (TAO) [10] by providing more powerful component-based abstractions using the specification, validation, packaging, configuration, and deployment techniques defined by the OMG CCM [6] and Deployment and Configuration (D&C) [11] specifications.…”
Section: Challenges Of Applying Qos-enabled Component Middleware mentioning
confidence: 99%
“…In conjunction with colleagues at Washington University [8], we have developed the Component-Integrated ACE ORB (CIAO) [9] CCM implementation. CIAO extends our previous work on The ACE ORB (TAO) [10] by providing more powerful component-based abstractions using the specification, validation, packaging, configuration, and deployment techniques defined by the OMG CCM [6] and Deployment and Configuration (D&C) [11] specifications.…”
Section: Challenges Of Applying Qos-enabled Component Middleware mentioning
confidence: 99%
“…Model-driven development (MDD) [21] is a generative software paradigm that combines • Domain-Specific Modeling Languages (DSMLs) whose type systems formalize the application structure, behavior, and requirements within particular domains, such as software defined radios, avionics mission computing, online financial services, warehouse and freight management, or even the domain of middleware platforms. DSMLs are described using metamodels, which define the relationships among concepts in a domain and precisely specify the key semantics and constraints associated with these domain concepts.…”
Section: Simplifying Autonomic System Development Via Mdd Techniquesmentioning
confidence: 99%
“…J3 consists of several MDD tools and autonomic computing frameworks, including (1) J2EEML, which captures the design of EJB applications, their quality of service (QoS) [21] requirements, and the autonomic adaptation strategies of their EJBs via a domain-specific modeling language (DSML) [14], (2) Jadapt, which is a J2EEML model interpreter that analyzes the QoS and autonomic properties of J2EEML models, and (3) JFense, which is an autonomic framework for monitoring, configuring, and resetting individual EJBs [6]. This paper describes the structure and functionality of J2EEML and shows how it simplifies autonomic system development by providing notations and abstractions that are aligned with autonomic computing, QoS, and EJB terminology, rather than low-level features of operating systems, infrastructure middleware platforms, and third-generation programming languages.…”
Section: Simplifying Autonomic System Development Via Mdd Techniquesmentioning
confidence: 99%
“…CIAO [10] is a QoS-enabled implementation of CCM (see Sidebar 1) developed at Washington University, St. Louis and Vanderbilt University to help simplify the development of performance-intensive software applications by enabling developers to declaratively provision QoS policies end-to-end when assembling a DRE system. CIAO adds component support to TAO [3], which is distribution middleware that implements key patterns [11] to meet the demanding QoS requirements of DRE systems.…”
Section: Step 1: Subject Applicationsmentioning
confidence: 99%