As far as communication goes, I'll only ever (as far as I know now) have to pass the userVO down from Tier #1 to Tier #3 but there is never Tier #2 to Tier #2 communication. What is the best method for that?
As far as project structure goes I was reading on this post and was wanting some clarification: http://forums.puremvc.org/index.php?topic=856.0
In reality you usually have several projects.
* One project for your main app,
* At least one for your modules (if not several that group modules, or even one per module).
* One or more library projects where you put classes that you share between the other projects so that they don't depend on each other or duplicate classes.
Compile your modules and libraries to make all their dependencies external, so that PureMVC, Pipes, Flex and any other dependencies are expected to be present in the main app, and aren't being compiled into your module.
Compile your main application to include these libraries. This may make the main app a little larger but the modules will be small and efficient.
1. So would I have the libraries in the main application and reference it in the sub applications (other projects)? Can you just reference a library and not have it in the build path? Or would I have a seperate project for the library rather than being in the main app?
2. So when do you keep different cores in a core folder in the main project and when do you break them out?
Going back to #4 in my previous post, I see how having modules in separate applications identifies them with their classes. Is there a way to do this if it is all in one application together?