Skip to content

EventDispatch implements the Mediator pattern, not the Observer pattern #2817

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

EventDispatch implements the Mediator pattern, not the Observer pattern #2817

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions components/event_dispatcher/introduction.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ or after a method is executed, without interfering with other plugins. This is
not an easy problem to solve with single inheritance, and multiple inheritance
(were it possible with PHP) has its own drawbacks.

The Symfony2 Event Dispatcher component implements the `Observer`_ pattern in
The Symfony2 Event Dispatcher component implements the `Mediator`_ pattern in
a simple and effective way to make all these things possible and to make your
projects truly extensible.

Expand Down Expand Up @@ -492,7 +492,7 @@ listener via the
Now, any listeners to ``store.order`` that have not yet been called will *not*
be called.

.. _Observer: http://en.wikipedia.org/wiki/Observer_pattern
.. _Mediator: http://en.wikipedia.org/wiki/Mediator_pattern
.. _Closures: http://php.net/manual/en/functions.anonymous.php
.. _PHP callable: http://www.php.net/manual/en/language.pseudo-types.php#language.types.callback
.. _Packagist: https://packagist.org/packages/symfony/event-dispatcher