1998
DOI: 10.1016/s0140-3664(97)00165-5
|View full text |Cite
|
Sign up to set email alerts
|

The design of the TAO real-time object request broker

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
141
0
1

Year Published

2000
2000
2007
2007

Publication Types

Select...
5
2
2

Relationship

4
5

Authors

Journals

citations
Cited by 411 publications
(143 citation statements)
references
References 8 publications
0
141
0
1
Order By: Relevance
“…RTZen also includes many of the performance and predictability enhancing techniques pioneered in ZEN [18][19][20] and TAO [21][22][23][24]. For example, RTZen's thread pool implements the Half-Sync/Half-Async pattern [9] to minimize complexity and allow high throughput, and the POA uses active-demux tables to allow O(1) demultiplexing of server-side objects.…”
Section: Scoped Memorymentioning
confidence: 99%
“…RTZen also includes many of the performance and predictability enhancing techniques pioneered in ZEN [18][19][20] and TAO [21][22][23][24]. For example, RTZen's thread pool implements the Half-Sync/Half-Async pattern [9] to minimize complexity and allow high throughput, and the POA uses active-demux tables to allow O(1) demultiplexing of server-side objects.…”
Section: Scoped Memorymentioning
confidence: 99%
“…The OMG Real-Time CORBA 1.2 specification (RTC1.2) [5] addresses limitations with the fixed-priority mechanisms specified in RTC1 byintroducing two new concepts to Real-time CORBA: (1) distributable threads that are used to map end-to-end QoS requirements to distributed computations across the endsystems they traverse and (2) a scheduling service architecture that allows applications to choose which mechanisms enforce task eligibility. To facilitate the study of standards-based dynamic scheduling middleware, we have implemented a RTC1.2 framework that enhances on our prior work with The ACE ORB (TAO) [6] (a widely-used open-source implementation of Real-time CORBA 1.0 [1]) and its Real-time Scheduling Service (which supports both static [7] and dynamic scheduling [8]). This paper describes how we designed and optimized the performance of our RTC1.2 Dynamic Scheduling framework to address the following design challenges for adaptive DRE systems:…”
Section: Solution Approachmentioning
confidence: 99%
“…The system architecture for our first case study included an OFP consisting of approximately 70 operations, the Boeing Bold Stroke avionics domain-specific middleware layer [16] built upon The ACE ORB (TAO) [6], the TAO Reconfigurable Scheduling Service [7,8], and the TAO Real-Time Event Service [17], configured for various scheduling strategies described in Sections 2 and 3. This middleware isolates applications from the underlying hardware and OS, enabling hardware or OS advances to be integrated more easily with the avionics application.…”
Section: Case Study 1 Effects Of Cancellation Of Non-critical Operationsmentioning
confidence: 99%
“…It is based on an extension of the TAO ORB [30] with the concept of architectural awareness, making explicit the architectural structure of a system in a causally connected way. Middleware configurations are defined in terms of prerequisite specifications, which represent the components of the platform and the dependencies among them.…”
Section: Related Workmentioning
confidence: 99%