Skip to main content Accessibility help

We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.

Close cookie message
×
Hostname: page-component-84b7d79bbc-l82ql Total loading time: 0 Render date: 2024-07-27T23:13:39.892Z Has data issue: false hasContentIssue false

Chapter 11 - Integrating Legacy Code—Wrapping

from Part III - OBJECT-ORIENTED CONSTRUCTION

Published online by Cambridge University Press:  07 September 2010

Scott W. Ambler
Scott W. Ambler
Affiliation:
AmbySoft Inc., Toronto
Get access

Summary

What We'll Learn in This Chapter

Why we need to wrap.

What the approaches to wrapping are.

When, and when not, to use the following wrapping technologies: C APIs, dynamic shared libraries, screen scraping, peer-to-peer, and the Common Object Request Broker Architecture (CORBA).

The trade-offs of wrapping.

Information technology shops of today have a huge investment in information technology; unfortunately, the vast majority of it isn't object oriented (OO). In the 1980's it is estimated that over $ 1 trillion was invested in information technology in the United States alone. Needless to say organizations are motivated to retain as much of this investment as possible. Wrapping is a technique in which you make non-OO technology appear to be OO by putting a layer of OO code around it, which is often a critical part of any significant OO project.

A wrapper is a collection of one or more classes that encapsulates access to technology that isn't object-oriented to make it appear as if it is. A wrapper class is any class that is part of a wrapper. Wrapping, as shown in Figure 11.1, is used to provide OO applications access to hardware, operating system features, procedure libraries, function libraries, and even legacy applications. Wrapping allows you to retain your investment in older, non-OO technology by allowing you to reuse it in the new OO applications that you develop.

Type
Chapter
Information
Building Object Applications that Work
Your Step-by-Step Handbook for Developing Robust Systems with Object Technology
 , pp. 343 - 360
Publisher: Cambridge University Press
Print publication year: 1997

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×