General talk about software patterns

[Messaging Design Pattern <dsheppard2k AT yahoo.com>]

Al,

Perhaps you could elaborate in terms of why you think the messaging design pattern is complex (specific examples, etc). I'd like to understand.  I believe it would benefit the discussion. I see it as a simple pattern (perhaps just me) with wide applicability .

Folks, let's get to the facts of the matter (MDP) based on reason and solid evidence/arguments. I think that we all agree that this is not a crazy idea. This is a fact. I think that if several of us think that way. We can convince the rest based on reason, solid evidence and facts. This would result in real benefits/gain. Also there may a better way of communicating the ideas behind the messaging pattern. I'd love to hear how this can be accomplished. BTW, I'm glad to hear that I'm not crazy after all ;-)


Best Regards,

--- On Tue, 12/14/10, Al Boldi <a1426z AT gawab.com> wrote:


Maybe I am missing something, but the MDP is definitely not a crazy idea.  And
yes, the MDP concept has been around for a long time, which should make it
eligible for a design pattern.

The only problem I see here is that the MDP is a complex pattern.

Complex patterns as opposed to simple patterns, like ITERATOR and VISITOR,
need to be decomposed into their respective simple patterns, to aid the
developer in the implementation of the complex pattern.  It is this
decomposition of the complex pattern that in turn should clarify many of the
possible interpretations of the complex pattern.

So, for the case of the MDP, has this decomposition be performed?


Thanks!

--
Al
-