We have a big bank environment based on a J2EE/Spring server and JSP/JQuery/Flex client. The Flex lays in a jsp template. We have many Flex project with hierarchicals runtime shared libraries layers.
We have an application that have many and many views, and we want to separate (modularize) the main application with groups of views in modules. In the past, in the same case we would have made rsl to achieve this but we analized in the last days the possibility to work with modules and integrate the modules in our framework.
The question is:
What are the pros and cons working with modules and working with rsl. I know the technical differences so the question is more an architectural question.
P.S. Sorry for my bad english
In Flex, an RSL is downloaded before the application starts. If the RSL is
not already cached, the end user has to wait longer to see the application.
Modules can be loaded at any time, even after the application starts. It is
a great way to defer the download of code and assets not needed at startup
Modules can be unloaded, RSLs cannot. Therefore modules help you manage
Modules that can be unloaded cannot share assets and data with other modules
unless the classes for the assets and data are in a common
You can load a module into the main applicationDomain which means it cannot
be unloaded, but then it will act like an RSL that got loaded after the
So depending on network speed (and don't forget intranet users working from
home over VPN and DSL), you might want to use both RSLs and modules. The
RSLs contain classes that almost every app will use, especially if the RSL
download time is not prohibitive. Everything else goes into modules and
classes that need to be shared between modules can be loaded into the main