Okay, I have made a first revision for a TaggedValve and Valve class.

There is no attachment on the forums here... so I will upload it on pastebin as a diff.

http://puremvc.pastebin.com/f3b7cf9be

Yeah, but what if a third-party wants a class from its module to be available for other modules to use? I think OSGi solves this, but I'm not sure. Also, I can try to create a select valve, I have a couple ideas.

Okay. That helps, but if you take the PipeWorks demo, all the modules were compiled into the same application, and there were helper classes inside the common and shell packages (LogMessage, LoggingJunctionMediator). That's fine, but for places where modules are written by third parties and loaded dynamically, you can't have a "common" package to agree on a format, as third-parties would need to have access to modify the common package.

I believe that making a ModuleJunction with a "sendMessageToModule" that sends a special message to the shell on a special pipe to be redirected to the correct module (if it exists) is the best way to do this. I should note that since this is an RIA, these modules are not DisplayObject modules; they add features to the RIA, like plug-ins.

What other options are there? I can override the sendMessage method to look for a module with those wanted pipes, so I don't have to keep adding pipes here and there. But I could do it the hard way and create a sort-of polygonal figure with each diagonal being a pipe going from one module to another. The idea is that each module requests for input pipes to be added to every other module, so the LoggerModule requests a STDLOG as well as its usual input.

I would like some sort of "select valve" that works like a TeeSplit except you can toggle outputs on or off, so you can control which of the output pipes it goes to. Hmm... maybe I could make that.

I have a question about Module to Module communication to Pipes. I am liking PureMVC and Pipes very much, but have some questions about how to accomplish Module to Module communication with Pipes.

I want to have a system where modules can communicate with the shell, and also with other modules. I have some general ideas about how to do this, but I want to know what is generally accepted to be the best way:

• On module load, go through the list of modules and have the Shell JunctionMediator go through the list of modules and add one or more input and output pipes for each module in the list against the module that was just initialized. This would require making a lot of pipes for simple messaging.
• Create a "RedirectJunction" with a "sendMessageToModule" method that sends a special message type to the shell for redirection toward the correct module.

Also, why would use more than one pipe per module and more than one message type? I guess I'm a little confused as how something would differ from the standard setup.