Architectural Support for Quality of Service for CORBA Objects
J. Zinky, D. Bakken, R. Schantz
{"title":"Architectural Support for Quality of Service for CORBA Objects","authors":"J. Zinky, D. Bakken, R. Schantz","doi":"10.1002/(SICI)1096-9942(1997)3:1<55::AID-TAPO6>3.0.CO;2-6","DOIUrl":null,"url":null,"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.","PeriodicalId":293061,"journal":{"name":"Theory Pract. Object Syst.","volume":"35 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"573","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Theory Pract. Object Syst.","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1002/(SICI)1096-9942(1997)3:1<55::AID-TAPO6>3.0.CO;2-6","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 573
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.
对CORBA对象服务质量的体系结构支持
CORBA是一种用于分布式对象计算的商业标准,在分布式程序的开发中显示出巨大的前景。它的接口描述语言(IDL)使对象能够独立于它们将要执行的底层编程语言、操作系统或计算机体系结构进行开发。虽然这在许多环境中是足够的,但部署在广域分布式系统中的程序遇到的条件比在单个地址空间或单个局域网中运行的程序更加恶劣和多变。在本文中,我们讨论了我们在开发和部署广域分布式对象应用程序和中间件时观察到的四个主要问题。首先,大多数程序的开发忽略了可变的广域条件。其次,当应用程序程序员试图处理这些条件时,他们会遇到很大的困难,因为这些苛刻的条件与他们习惯处理的本地对象的条件不同。第三,IDL隐藏了关于任何对象实现必须做出的权衡的信息。第四,目前还没有办法系统地重用处理这些条件的现有技术组件,因此代码共享变得不切实际。在本文中,我们还描述了我们的体系结构,CORBA对象的服务质量(QuO),我们开发该体系结构是为了克服这些限制,并通过向CORBA对象提供QoS抽象来集成它们的解决方案。首先,它使这些条件成为一流的实体,并将它们的知识随时间、空间和来源进行整合。其次,它通过掩蔽来减少方差。第三,它公开了对象实现的关键设计决策以及如何使用它。第四,它支持各种架构组件的重用,并自动生成其他组件。©1997 John Wiley & Sons, Inc
本文章由计算机程序翻译,如有差异,请以英文原文为准。