Glossary

This glossary defines many of the terms that we use frequently throughout the book. All terms are related to various aspects of concurrent and networked software. When a definition consists of other terms in the glossary we italicize these terms.

We have omitted terminology used in only one context, for example the network management terms from the Extension Interface and Asynchronous Completion Token patterns. Where such terms need a definition, we present them in context rather than including them here. For completeness, we have also included common terms, such as ‘pattern’, ‘software architecture’, and ‘idiom’, that were explained in depth in various sections of [POSA1].

Abstract Class

A class that does not implement all the methods defined in its interface. An abstract class defines a common abstraction for its subclasses.

Abstract Component

A component that specifies an interface for other components. An abstract component can either be explicit, such as an abstract class, or implicit, such as a class parameter of a C++ template function. Abstract components form the basis for exploiting polymorphism and implementing flexible systems. This term is used in the same way as abstract class, to avoid restricting the pattern to object-oriented languages.

Abstract Method

The declaration of an operation of a class that must be defined by a subclass.

Active Connection Establishment

The connection role played by a peer application that initiates a connection to a remote peer. ...

Get Pattern-Oriented Software Architecture, Volume 2, Patterns for Concurrent and Networked Objects now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.