By Topic

Middleware versus native OS support: architectural considerations for supporting multimedia applications

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

4 Author(s)
Shenoy, P. ; Dept. of Comput. Sci., Massachusetts Univ., Amherst, MA, USA ; Hasan, S. ; Kulkarni, P. ; Ramamritham, K.

In this paper, we examine two architectural alternatives-native OS support versus middleware-for supporting multimedia applications. Specifically, we examine whether extensions to OS functionality are necessary for supporting multimedia applications, or whether much of these benefits can be accrued by implementing resource management mechanisms in a middleware system. To answer these questions, we use QLinux and TAO as representative examples of a multimedia operating system and a multimedia middleware, respectively, and examine their effectiveness in supporting distributed applications. Our results show that although the run-time overheads of a middleware can impact application performance, middleware resource management mechanisms can, nevertheless, be as effective as native OS mechanisms for many applications. We also find OS kernel-based mechanisms to be more effective then middleware systems at providing application isolation and at preventing applications from interfering with one another.

Published in:

Real-Time and Embedded Technology and Applications Symposium, 2002. Proceedings. Eighth IEEE

Date of Conference: