Various motivations include looser coupling, extensibility, resilience. Also, pub/sub allows modeling frameworks as regular objects.
On Mon, Mar 19, 2012 at 3:35 PM, Casey Ransberger <[email protected]>wrote: > Here's the real naive question... > > I'm fuzzy about why objects should receive messages but not send them. I > think I can see the mechanics of how it might work, I just don't grok why > it's important. > > What motivates? Are we trying to eliminate the overhead of ST-style > message passing? Is publish/subscribe easier to understand? Does it lead to > simpler artifacts? Looser coupling? Does it simplify matters of concurrency? > > I feel like I'm still missing a pretty important concept, but I have a > feeling that once I've grabbed at it, several things might suddenly fit and > make sense. > _______________________________________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/listinfo/fonc > -- bringing s-words to a pen fight
_______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
