Notification Server

Download 133,61 Kb.
Hajmi133,61 Kb.
1   2   3   4   5   6

Thanks are due to Steven Abell, Donald Griffin, and Brad Appleton for giving helpful hints for improvement.

[BMRSS96] Buschmann, F.; Meunier, R.; Rohnert, H.; Sommerlad, P.; Stal, M.:

Pattern-Oriented Software Architecture: A System of Patterns.

Jon Wiley & Sons, 1996
[GHJV94] Gamma, E.; Helm, R.; Johnson, R.; Vlissides, J.:

Design Patterns: Elements of Reusable Object-Oriented Software.

Addison-Wesley, 1994
[OMG94] Object Services Architecture.

Object Management Group, December 1994

[OMG95] The Common Object Request Broker: Architecture and Specification

Object Management Group, July 1995

[OMG96] CORBAservices: Common Object Services Specification.

Object Management Group, March 1996

[PHS98] Pyarali, I.; Harrison, T.; Schmidt, D.C.:

Asynchronous Completion Token.

In: Pattern Languages of Program Design 3.

Addison-Wesley, 1998

1 To my mind the context can be widened to passive resources in general ...

2 Command(233): Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.

3 Observer(293): Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically ([GHJV94]).

4 Publisher-Subscriber(339): The Publisher-Subscriber design pattern helps to keep the state of cooperating components synchronized. To achieve this it enables one-way propagation of changes: one publisher notifies any number of subscribers about changes to its state ([BMRSS96]).

5 Asynchronous Completion Token: To efficiently associate state with the completion of asynchronous operations ([PHS98]).

notification server, page of

Download 133,61 Kb.
1   2   3   4   5   6

Download 133,61 Kb.