Comments on: PureMVC Pipes

By: Joshua

Joshua — Thu, 26 Mar 2009 03:50:27 +0000

Using the flex doc approach is valid in that you define an interface for the clients to implement. This defines a ‘contract’ that the module will then fulfill.

Regardless of which approach you use, you can have the loaded app send a message up to the main app, and have the app route the message back down to the loaded modules.

If your not familiar w/PureMVC I’d suggest writing a small proof of concept app to get this wired up. Once you have that you can determine if you’d like to implement as-is or move over to PureMVC (pipes).

Josh

By: Lorenzo

Lorenzo — Mon, 23 Mar 2009 15:42:44 +0000

Hi Joshua,

thanks for the reply…

i would create a small application, like a portal, where modules are loaded and unloaded run-time.
in the app if two modules are “compatibles” they can pass data each other..
so could you suggest me the best way to rich modules to modules communication..
in the past week i’ve read about pureMVC and pipes utility…i think it could be the right way to follow (even if it’s more difficult), instead of using interface and references (as suggested into the adobe flex doc).

thanks again
Lorenzo

By: Joshua

Joshua — Wed, 04 Mar 2009 14:06:56 +0000

Lorenzo, how you architect the communication depends on your use case. You could send your messages ‘up’ to the main app (from the loaded swf) and back down to the other loaded swfs (see http://www.joshuaostrom.com/2008/06/17/pipe-demo-mortgage-app/ for an example). You could also communicate directly, although if your app grows too much (loading numerous modules) I’d recommend a common message ‘bus’ over point-to-point communication flows

By: Lorenzo

Lorenzo — Wed, 04 Mar 2009 09:39:21 +0000

Hi Joshua,

can you explain with a simple example the module to module communication?

thanks in advance
Regards
Lorenzo