﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Design patterns in the test of time: Mediator</title><description>Chandan,
I am sorry, but I am not going to even try to comment on something like that.
I don't have a clue about ActionScript, far less about a specific framework in ActionScript.</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment10</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment10</guid><pubDate>Mon, 28 Jan 2013 14:12:47 GMT</pubDate></item><item><title>Chandan commented on Design patterns in the test of time: Mediator</title><description>What about the mediators in PureMvc framework in ActionScript -It mediates between UI and command -Command in turn interacts with Server  via a Proxy</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment9</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment9</guid><pubDate>Mon, 28 Jan 2013 14:05:34 GMT</pubDate></item><item><title>Ayende Rahien commented on Design patterns in the test of time: Mediator</title><description>Euproric,
Think about the distinction between Facade &amp; Mediator, or Stategy &amp; State.
Those are really subtle distinctions, but they need different names, to express their differences.
To call MessageBus a Mediator is the same, except the gap is FAR larger.</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment8</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment8</guid><pubDate>Fri, 25 Jan 2013 07:12:58 GMT</pubDate></item><item><title>Euproric commented on Design patterns in the test of time: Mediator</title><description>Ayende, I would like to hear your explanation about what diferentiates Mediator and MessageBus/Event Aggregator.</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment7</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment7</guid><pubDate>Thu, 24 Jan 2013 15:18:02 GMT</pubDate></item><item><title>Ayende Rahien commented on Design patterns in the test of time: Mediator</title><description>Guys,
I don't consider message passing to be mediator.
It is own separate thing.</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment6</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment6</guid><pubDate>Tue, 22 Jan 2013 07:47:55 GMT</pubDate></item><item><title>Judah Gabriel Himango commented on Design patterns in the test of time: Mediator</title><description>Yep, the MessageBus/PubSub is a mediator, and it's commonly found in MVVM frameworks to communicate between view models. It's also used in web apps to communicate between components in a page.

I use Knockout.PostBox (https://github.com/rniemeyer/knockout-postbox) to do pub/sub in my web apps. Very slick. Components (e.g. observables) communicate by publishing messages on the mediator object, ko.postbox.

I even use it for application commands. So my Song object can simply call ko.postbox.publish("Play", this) to tell my application to start playing that song. It doesn't care who is listening for that command, thus decoupling the implementation from the usage. Works out nicely.</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment5</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment5</guid><pubDate>Mon, 21 Jan 2013 23:06:03 GMT</pubDate></item><item><title>Dmitry commented on Design patterns in the test of time: Mediator</title><description>I agree with Trystan that a non-distributed message/event bus or a command queue should be considered a mediator.</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment4</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment4</guid><pubDate>Mon, 21 Jan 2013 19:40:42 GMT</pubDate></item><item><title>mravinale commented on Design patterns in the test of time: Mediator</title><description>How about:
The Messenger class of Mvvm Light?
The Event Agreggator implementation of Caliburn? 
or this implementation in Js? http://thejacklawson.com/Mediator.js/

I think that can be very useful when you need to build loosely coupled components.



</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment3</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment3</guid><pubDate>Mon, 21 Jan 2013 18:25:20 GMT</pubDate></item><item><title>Trystan commented on Design patterns in the test of time: Mediator</title><description>Isn't a service bus, or any kind of messaging system, a mediator? I'd also consider the events and callbacks parts of jQuery an example of the mediator pattern. I've found both to be very useful.
I've also written small classes hook two services together so I can test that they're wired together correctly. Isn't that a mediator?</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment2</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment2</guid><pubDate>Mon, 21 Jan 2013 17:49:45 GMT</pubDate></item><item><title>Ricardo Peres commented on Design patterns in the test of time: Mediator</title><description>One example of a Mediator that we use everyday is the ASP.NET web forms page: it knows and performs operations in controls that exist inside of it. Don't you agree?</description><link>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment1</link><guid>http://ayende.com/160737/design-patterns-in-the-test-of-time-mediator#comment1</guid><pubDate>Mon, 21 Jan 2013 16:19:54 GMT</pubDate></item></channel></rss>