General talk about software patterns

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

Al,

1) No. Observer and messaging are two separate design patterns (concepts).

3) If we think in terms of a realistic model, we realize that messaging (interchange of information) is everywhere around us. Therefore MDP can be applied to a wide variety of problems and applications. The MDP papers presents specific examples (Known uses section):


- Messaging Design Pattern (MDP) and pattern implementation -
17th conference on Pattern Languages of Programs (PLoP 2010).
https://jt.dev.java.net/files/documents/5553/150311/designPatterns.pdf

-  Messaging Design Pattern and a distributed Component/Service Model
https://jt.dev.java.net/files/documents/5553/149793/MDPdistributedModel.pdf
 
Some specific applications include Distributed Component Technologies, Web Services, ESB, BPEL technologies, design pattern implementation, messaging frameworks, etc.
 
In terms of performance and resource usage, MDP is very light and efficient. Keep in mind that messaging (core functionality) can be implemented with a single messaging interface:

public interface JtInterface  {
/**
  * Jt messaging interface used for the implementation
  * of the messaging design pattern.
  * Process an input message and return a reply (output message)
  */

  Object processMessage (Object message);
}

The Jt design pattern framework (based on MDP) runs on large servers as well as small devices (under Android) without performance degradation or memory issues.  In summary, messaging as a natural concept and design pattern seems to be very efficient and widely applicable (great designer).

Feel free to send any additional comments or questions that you may have.

Regards

 
P.S. Generics may be used for type checking. Similar to the iterator
implementation. I mention it because several people have brought it up:

interface Iterator<E> {
   E next();
   boolean hasNext();
}

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

From: Al Boldi <a1426z AT gawab.com>
Subject: MDP feasibility questions (was: Messaging Design Patterns (MDP) reusability and QA)
To: "Messaging Design Pattern" <dsheppard2k AT yahoo.com>
Cc: patterns-discussion AT cs.uiuc.edu
Date: Saturday, December 11, 2010, 3:46 PM

Messaging Design Pattern <dsheppard2k AT yahoo.com> wrote:
> I'm glad that the real world analogies served their purpose. At the very
> least they encouraged the reader to think in terms of a realistic software
> model (based on messaging) that mimics the world around us. The main goal
> of this discussion is the to clarify or expand on specific points not
> covered by the paper.
>
> In terms of reusability, there are several areas where  the messaging
> design pattern  (MDP) provides improvements:

Can the MDP be used to replace the Observer Design Pattern?

If so, would the system be easier or harder to implement in the long-run?

What about performance and resource usage?

When is the MDP applicable, and when is it not applicable?


Thanks!

--
Al