Content deleted Content added
Rescuing 3 sources and tagging 0 as dead.) #IABot (v2.0.9.5 |
Split Publish–subscribe pattern and Observer pattern -- they are distinct |
||
| (One intermediate revision by one other user not shown) | |||
Line 7:
;[[Blackboard design pattern]]
: Provides a computational framework for the design and implementation of systems that integrate large and diverse specialized modules, and implement complex, non-deterministic control strategies
;[[Chain
: Command objects are handled or passed on to other objects by logic-containing processing objects
;[[Command pattern]]
Line 33:
: Designed to act as a default value of an object
<dl>
<dt>[[Observer pattern]]</dt>
<dd>Defines a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically. The variant '''weak reference pattern''' decouples an observer from an observable to avoid memory leaks in environments without automatic weak references.<ref>{{cite web |last=Nakashian |first=Ashod |date=2004-04-11 |title=Weak Reference Pattern |url=http://c2.com/ |url-status=bot: unknown |archive-url=https://web.archive.org/web/20110303085751/http://c2.com/ |archive-date=2011-03-03 |access-date=2012-05-21 |publisher=c2.com}}</ref></dd></dl>
;[[Protocol stack]]
: Communications are handled by multiple layers, which form an encapsulation hierarchy<ref>{{cite web
Line 64 ⟶ 46:
|url-status = bot: unknown
}}</ref>
;[[Publish–subscribe pattern]]<dd>A messaging pattern where senders (publishers) and receivers (subscribers) are decoupled via message topics and brokers. Commonly used in distributed systems, this pattern supports asynchronous, many-to-many communication.</dd>
;[[Scheduled-task pattern]]
: A task is scheduled to be performed at a particular interval or clock time (used in [[real-time computing]])
| |||