From 36da1d92558eaae6e8a310f5d43f0fbca5f578bf Mon Sep 17 00:00:00 2001 From: John Kary Date: Thu, 11 Jul 2013 11:56:47 -0500 Subject: [PATCH] EventDispatch implements the Mediator pattern, not the Observer pattern --- components/event_dispatcher/introduction.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/components/event_dispatcher/introduction.rst b/components/event_dispatcher/introduction.rst index 82fb8625e1d..defaecb5354 100644 --- a/components/event_dispatcher/introduction.rst +++ b/components/event_dispatcher/introduction.rst @@ -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. @@ -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