Home > Store

Advanced CORBA® Programming with C++

Register your product to gain access to bonus material or receive a coupon.

Advanced CORBA® Programming with C++


  • Sorry, this book is no longer in print.
Not for Sale



  • In-depth coverage of IDL, including common idioms and design trade-offs.
  • Complete and detailed explanations of the Life Cycle, Naming, Trading, and Event Services.
  • Discussion of IIOP and implementation repositories.
  • Insight into the dynamic aspects of CORBA, such as dynamic typing and the new DynAny interfaces.
  • Advice on selecting appropriate application architectures and designs.
  • Detailed, portable, and vendor-independent source code.


  • Copyright 1999
  • Dimensions: 7-3/8" x 9-1/4"
  • Pages: 560
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-37927-9
  • ISBN-13: 978-0-201-37927-3

Here is the CORBA book that every C++ software engineer has been waiting for. Advanced CORBA® Programming with C++ provides designers and developers with the tools required to understand CORBA technology at the architectural, design, and source code levels. This book offers hands-on explanations for building efficient applications, as well as lucid examples that provide practical advice on avoiding costly mistakes. With this book as a guide, programmers will find the support they need to successfully undertake industrial-strength CORBA development projects.

The content is systematically arranged and presented so the book may be used as both a tutorial and a reference. The rich example programs in this definitive text show CORBA developers how to write clearer code that is more maintainable, portable, and efficient. The authors' detailed coverage of the IDL-to-C++ mapping moves beyond the mechanics of the APIs to discuss topics such as potential pitfalls and efficiency. An in-depth presentation of the new Portable Object Adapter (POA) explains how to take advantage of its numerous features to create scalable and high-performance servers. In addition, detailed discussion of advanced topics, such as garbage collection and multithreading, provides developers with the knowledge they need to write commercial applications.

Other highlights

  • In-depth coverage of IDL, including common idioms and design trade-offs
  • Complete and detailed explanations of the Life Cycle, Naming, Trading, and Event Services
  • Discussion of IIOP and implementation repositories
  • Insight into the dynamic aspects of CORBA, such as dynamic typing and the new DynAny interfaces
  • Advice on selecting appropriate application architectures and designs
  • Detailed, portable, and vendor-independent source code



Source Code

Source Code and Online Resources

Source code for the examples in the book


Author's Site

Click below for Author's Site related to this title:

Sample Content

Downloadable Sample Chapter

Click below for Sample Chapter(s) related to this title:
Sample Chapter 6

Table of Contents


1. Introduction.


Organization of the Book.

CORBA Version.

Typographical Conventions.

Source Code Examples.

Vendor Dependencies.

Contacting the Authors.


2. An Overview of CORBA.


The Object Management Group.

Concepts and Terminology.

CORBA Features.

Request Invocation.

General CORBA Application Development.


3. A Minimal CORBA Application.

Chapter Overview.

Writing and Compiling an IDL Definition.

Writing and Compiling a Server.

Writing and Compiling a Client.

Running Client and Server.



4. The OMG Interface Definition Language.

Chapter Overview.



Source Files.

Lexical Rules.

Basic IDL Types.

User-Defined Types.

Interfaces and Operations.

User Exceptions.

System Exceptions.

System Exceptions or User Exceptions?

Oneway Operations.




Forward Declarations.


Names and Scoping.

Repository Identifiers and pragma Directives.

Standard Include Files.

Recent IDL Extensions.


5. IDL for a Climate Control System.

Chapter Overview.

The Climate Control System.

IDL for the Climate Control System.

The Complete Specification.

6. Basic IDL-to-C++ Mapping.

Chapter Overview.


Mapping for Identifiers.

Mapping for Modules.

The CORBA Module.

Mapping for Basic Types.

Mapping for Constants.

Mapping for Enumerated Types.

Variable-Length Types and _var Types.

The String_var Wrapper Class.

Mapping for Wide Strings.

Mapping for Fixed-Point Types.

Mapping for Structures.

Mapping for Sequences.

Mapping for Arrays.

Mapping for Unions.

Mapping for Recursive Structures and Unions.

Mapping for Type Definitions.

User-Defined Types and _var Classes.


7. Client-Side C++ Mapping.

Chapter Overview.


Mapping for Interfaces.

Object Reference Types.

Life Cycle of Object References.

Semantics of _ptr References.


ORB Initialization.

Initial References.

Stringified References.

The Object Pseudo-Interface.

_var References.

Mapping for Operations and Attributes.

Parameter Passing Rules.

Mapping for Exceptions.

Mapping for Contexts.


8.Developing a Client for the Climate Control System.

Chapter Overview.


Overall Client Structure.

Included Files.

Helper Functions.

The main Program.

The Complete Client Code.


9. Server-Side C++ Mapping.

Chapter Overview.


Mapping for Interfaces.

Servant Classes.

Object Incarnation.

Server main.

Parameter Passing Rules.

Raising Exceptions.

Tie Classes.


10. Developing a Server for the Climate Control System.

Chapter Overview.


The Instrument Control Protocol API.

Designing the Thermometer Servant Class.

Implementing the Thermometer Servant Class.

Designing the Thermostat Servant Class.

Implementing the Thermostat Servant Class.

Designing the Controller Servant Class.

Implementing the Controller Servant Class.

Implementing the Server Main Function.

The Complete Server Code.


11. The Portable Object Adapter.

Chapter Overview.


POA Fundamentals.

POA Policies.

POA Creation.

Servant IDL Type.

Object Creation and Activation.

Reference, ObjectId, and Servant.

Object Deactivation.

Request Flow Control.

ORB Event Handling.

POA Activation.

POA Destruction.

Applying POA Policies.


12. Object Life Cycle.

Chapter Overview.


Object Factories.

Destroying, Copying, and Moving Objects.

A Critique of the Life Cycle Service.

The Evictor Pattern.

Garbage Collection of Servants.

Garbage Collection of CORBA Objects.



13. GIOP, IIOP, and IORs.

Chapter Overview.

An Overview of GIOP.

Common Data Representation.

GIOP Message Formats.

GIOP Connection Management.

Detecting Disorderly Shutdown.

An Overview of IIOP.

Structure of an IOR.

Bidirectional IIOP.


14. Implementation Repositories and Binding.

Chapter Overview.

Binding Modes.

Direct Binding.

Indirect Binding via an Implementation Repository.

Migration, Reliability, Performance, and Scalability.

Activation Modes.

Race Conditions.

Security Considerations.



15. C++ Mapping for Type Any.

Chapter Overview.


Type Any C++ Mapping.

Pitfalls in Type Definitions.


16. Type Codes.

Chapter Overview.


The TypeCode Pseudo-Object.

C++ Mapping for the TypeCode Pseudo-Object.

Type Code Comparisons.

Type Code Constants.

Type Code Comparison for Type Any.

Creating Type Codes Dynamically.


17. Type DynAny.

Chapter Overview.


The DynAny Interface.

C++ Mapping for the DynAny Pseudo-Object.

Using DynAny for Generic Display.

Obtaining Type Information.



18. The OMG Naming Service.

Chapter Overview.


Basic Concepts.

Structure of the Naming Service IDL.

Semantics of Names.

Naming Context IDL.


Pitfalls in the Naming Service.

The Names Library.

Naming Service Tools.

What to Advertise.

When to Advertise.

Federated Naming.

Adding Naming to the Climate Control System.


19. The OMG Trading Service.

Chapter Overview.


Trading Concepts and Terminology.

IDL Overview.

The Service Type Repository.

The Trader Interfaces.

Exporting Service Offers.

Withdrawing Service Offers.

Modifying Service Offers.

The Trader Constraint Language.

Importing Service Offers.

Bulk Withdrawal.

The Admin Interface.

Inspecting Service Offers.

Exporting Dynamic Properties.

Trader Federation.

Trader Tools.

Architectural Considerations.

What to Advertise.

Avoiding Duplicate Service Offers.

Adding Trading to the Climate Control System.


20. The OMG Event Service.

Chapter Overview.


Distributed Callbacks.

Event Service Basics.

Event Service Interfaces.

Implementing Consumers and Suppliers.

Choosing an Event Model.

Event Service Limitations.



21. Multithreaded Applications.

Chapter Overview.


Motivation for Multithreaded Programs.

Fundamentals of Multithreaded Servers.

Multithreading Strategies.

Implementing a Multithreaded Server.

Servant Activators and the Evictor Pattern.


22. Performance, Scalability, and Maintainability.

Chapter Overview.


Reducing Messaging Overhead.

Optimizing Server Implementations.

Federating Services.

Improving Physical Design.


Appendix A: Source Code for the ICP Simulator.


Transient Simulator Code.

Persistent Simulator Code.

Appendix B: CORBA Resources.

World Wide Web.


Mailing Lists.


Index. 0201379279T10252001


For years, both of us have been (and still are) teaching CORBA programming with C++ to software engineers all over the world. One of the most frequently asked questions in our courses is, ''Where can I find a book that covers all this?'' Although many books have been written about CORBA, most of them focus on high-level concepts and do not address the needs of software engineers. Even though CORBA is conceptually simple, the devil lies in the detail. Or, more bluntly, books focusing on high-level concepts are of little use when you must find out why your program is dumping core.

To be sure, there are resources available about CORBA, such as newsgroups, Web pages, and the Object Management Group (OMG) specifications. However, none of them really meets the needs of a programmer who must get the code to work (and preferably by yesterday). We wrote this book so that there would finally be a tutorial and reference that covers CORBA programming with C++ at the level of detail required for real-life software development. (And, of course, we wrote it so that we would have a good answer for our students.)

Writing such a book is a tall order. Explaining the CORBA specification and APIs is one thing, and it's a necessary part of the book. However, knowing the various APIs will not, by itself, make you a competent programmer (only a knowledgeable one). To be competent, you need not only knowledge of the mechanics of the platform but also an understanding of how the different features interact. You must combine them effectively to end up with an application that performs and scales well and is maintainable, extensible, portable, and deployable.

To help you become competent (as opposed to merely knowledgeable), we go beyond the basics in a number of ways. For one thing, we provide advice as to what we consider good (and bad) design, and we make no attempt to hide problems with CORBA (which, like any other complex software system, has its share of wrinkles). Second, we go beyond the APIs by explaining some of CORBA's internal mechanisms. Even though you can use an ORB without knowing what goes on under the hood, it is useful to understand these mechanisms because they have a profound influence on how well (or how poorly) an application will perform. Third, we devote considerable space to a discussion of the merits of various design decisions; typically, when a design provides a gain in one area it also involves a loss in another. Understanding these trade-offs is crucial to building successful applications. And fourth, where appropriate, we make recommendations so that you are not left without guidance.

Inevitably, our approach required us to make value judgments, and, just as inevitably, a number of people will disagree with at least some of the recommendations we make. Whether you agree or disagree with us, you should still profit from our approach: if you agree, you can stick to the advice we give; if you disagree, the discussion will have at least encouraged you to think about the topic and form your own opinion. Either way, you are better off than you would be with a book that just dumps the facts on you without providing the deeper insight required to use them.


This book is not a beginner's book, in the sense that we do not devote much space to explaining the structure of the OMG or the pecification adoption process. We also do not provide a high-level overview of the architectural goals of CORBA or all its services and facilities (see 31 for a high-level overview). Instead, we assume that you want to know how to write real CORBA applications with C++. Despite the lack of overview material, you should be able to follow the material even if you have never seen CORBA before. If you have experience in network programming or have used another RPC platform, you will find it easy to pick things up as you go.

Much of this book consists of source code, so we expect you to be literate in C++. However, you do not need to be a C++ guru to follow the code. We have avoided obscure or little-understood features of C++, preferring clarity to cleverness. If you understand inheritance, virtual functions, operator overloading, and templates (not necessarily in intricate detail), you will have no problems. Some of the source code uses the Standard Template Library (STL), which is now part of the ISO/IEC C++ Standard. We have limited ourselves to very simple uses of this library, so you should be able to understand the source code even if you have never seen STL code before.

If you have never written threaded code, you will find the chapter on writing threaded servers tough going. Unfortunately, there was not enough room to provide an introduction to programming with threads. However, the Bibliography lists a number of excellent books on the topic.

Despite our best efforts to show realistic and working source code, we had to make a number of compromises to keep code examples understandable and of manageable size. When we demonstrate a particular feature, we often use straightline code, whereas in a realistic application the code would better be encapsulated in a class or helper function. We have also minimized error handling to avoid obscuring the flow of control with lots of exception handlers. We chose this approach for didactic purposes; it does not imply that the code pretends to reflect best possible engineering practice. (The Bibliography lists a number of excellent books that cover source code design in great detail.)

Scope of this Book

OMG members are continually improving CORBA and adding new features. As a result, available ORB implementations conform to different revision levels of the specification. This book covers CORBA 2.3. (At the time of writing, CORBA 2.3 is being finalized by the OMG.) Throughout the text, we indicate new features that may not yet be available in your ORB implementation; this allows you to restrict yourself to an earlier feature set for maximum portability.

Despite its size, our main regret is that this book is too short. Ever-increasing page counts and ever-closer deadlines forced us to drop chapters on the Dynamic Invocation Interface (DII), the Dynamic Skeleton Interface (DSI), and the Interface Repository (IFR). Fortunately, the vast majority of applications do not need those features, so dropping these chapters is not much of a loss. If your application happens to require the dynamic interfaces, the background we provide here will enable you to easily pick up what you need from the CORBA specification. Another feature notable by its absence is Objects-By-Value (OBV). We chose not to cover OBV because it is too new for anyone to have any substantial engineering experience with it. In addition, at the time of writing, there are still a number of technical wrinkles to be ironed out and we expect the OBV specification to undergo further changes before it settles down.

Size and time limitations also meant that we could not cover every possible CORBA service. For example, we did not cover the Transaction Service or Security Service because each of them would require a book of its own. Rather than being complete, we have restricted ourselves to those services that are most essential for building applications: the Naming, Trading, and Event Services. We cover those services in more detail than any other publication we are aware of.

An important part of this book is the presentation of the Portable Object Adapter (POA), which was added in CORBA 2.2. The POA provides the server-side source code portability that was missing from the (now deprecated) Basic Object Adapter. The POA also provides a number of features that are essential for building high-performance and scalable applications. We have therefore paid particular attention to showing you how to use the POA effectively in your designs.

Overall, we believe this book offers the most comprehensive coverage to date of CORBA programming with C++. We have arranged the material so that you can use the book both as a tutorial and as a reference. Our hope is that after the first reading, you will have this book open at your side when you are sitting at your terminal. If so, we will have achieved our goal of creating a book that is used by real engineers to build real applications.


As with any book, the authors are only part of the story, and this is the place to thank the large number of people who have contributed to making this book possible. At Addison Wesley Longman, Mike Hendrickson and our editor, Deborah Lafferty, believed us when we told them that this book needed to be written. Without their faith in us, you would not be reading this. Brian Kernighan reviewed several drafts and made us redo the job where necessary. His clarity of thought and critical eye have greatly improved this book. John Fuller and Genevieve Rajewski, our production editors, put up with all our naive questions and enabled two amateurs to take a book to camera-ready stage. Our copy editor, Betsy Hardinger, edited every page in this book with meticulous attention to detail. Her efforts taught us more about clarity of style than we thought possible.

Particular thanks go to Colm Bergin, Jonathan Biggar, Bart Hanlon, Jishnu Mukerji, and Doug Schmidt, our expert reviewers. They read the entire manu script and spotted many problems that would have otherwise gone unnoticed. Their comments kept us honest throughout. Alan Shalloway reviewed the book from the perspective of a newcomer and made valuable suggestions on how to improve the presentation of some of the more difficult topics.

Todd Goldman and Tim Gill from Hewlett-Packard gave us permission to draw on earlier ORB training material written by Michi. John Vinoski and Dan Rabideau of Green Bay Engraving take credit for designing the Mabius strip on the cover.

We are grateful to Steve's employer, IONA Technologies, for allowing us to use the next generation of their Orbix product (called ''ART'') to develop and test our code examples. Their generosity provided us with the opportunity to make sure that our examples were correct and functional. The fact that ART conforms to CORBA 2.3 allowed us to target the most recent version of the CORBA specification available as of this writing.

We also would like to thank the many contributors to comp.object.corba and the corba-dev mailing list. The discussions there have influenced much of the content of this book.

A number of people have provided feedback, corrections, and constructive criticism since the first printing of this book. Rather than list them all here (and have to keep updating this Preface for each new printing), we have placed a list of everyone who contributed at http://www.triodia.com/staff/michi/advanced_corba/acknowledgments.html. Our thanks go to all these people for helping to make this a better book.

Michi's Acknowledgments

I would like to thank my former employer, DSTC Pty Ltd, for providing me with an environment that was conducive to writing. Joachim Achtzehnter, Martin Chilvers, Wil Evers, Ted McFadden, and Michael Neville reviewed parts of the manuscript and made valuable suggestions for improvement. Particular thanks go to David Jackson, who read all my drafts and made sure that loose ends were not allowed to remain hanging. Finally, I would like to thank my wife, Jocelyn, and our son, Tyson, for their love and encouragement. Without their support and patience, this book would have never been written.

Steve's Acknowledgments

I would like to thank my employer, IONA Technologies, for supporting my efforts to write this book, which occasionally kept me away from the office. In particular, I would like to thank Barry Morris for his support and encouragement, Stephen Keating for taking up the slack when I had to miss work because of all-night writing sessions, and the whole IONA Boston product development team for their patience and support.

I would also like to thank Bart Hanlon, who not only reviewed this book but also was my manager at my former employer, for continually encouraging me for several years to tackle this project and for teaching me a lot about tackling projects in general. In the technical realm, I have learned from many people over the course of my career, but I owe much to John Morris, Craig Bardenheuer, Denis deRuijter, Dale LaBossiere, Tom Moreau, and Bob Kukura, who at one time or another greatly influenced my education in the realms of distributed systems and engineering in general. I would also like to thank my C++ Report co-columnist, Doug Schmidt, a true technical visionary whose work in object-oriented network programming, C++ frameworks, and CORBA has paved the way for books such as this one. He not only helped review this book, but also agreed to let me use material from our columns in writing it.

Finally, without the support of my family, I would have never been able to even consider writing this book. I'd like to thank my wife, Cindy, and our children, Ryan and Erin, for putting up with my extremely long hours and days of writing and working. Thanks also to my parents, Ed and Dooley, who have always supported me with their seemingly limitless patience and love. I also owe my brother, John, a special thanks for his wonderful artwork on our book cover.

Michi Henning and Steve Vinoski
October 1998




Click below for Errata related to this title:

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020