Loading RSLs from Modules

Question

For a while I've been wanting to be able to load an RSL from a Module.  The reason for this is that some modules require some RSL but that RSL is not needed in the MainApp.
I've googled alot on this subject and can't find any information that will show that this is possible, but now reading up on the enhancements of the Hero Sdk (http://opensource.adobe.com/wiki/display/flexsdk/RSL+Enhancements) it seems to be possible.
To be specific here is a quote from the info
3.   Going into Flex 4 we only expected sub-applications and modules to  re-use the RSLs loaded by the main application. But now we see modules  that are being used to load custom RSLs. Expecting the main application  to load all of the RSLs won't work anymore. We are also seeing cases  where modules want to be independent of the application and load all the  RSLs it needs without regard for which RSLs the application is loading.  Today this can result in multiple loads of the same RSL.
From reading that, it is possible.  Can anyone please point me in the direction on to how to acomplish that.  How to load an RSL that a module needs when loading the module?
Thanks,
Art

Answer 1

In 2008 and 2009 I was heavily involved in trying to develop modular Flex and AIR applications.  I have not been heavily involved for the past 10 months, so I don't know whether I can offer any help or not.  Some things have changed with Flex 4 and AIR 2, and while I have only spent a couple of days trying to catch up, it is very clear that Flex 4 and AIR 2 ended up being surprisingly different from what I was doing with Flex 3.3, AIR 1.5 and Gumbo.
If you would like to chat about it, please send me an email:  tcorbet at ix.netcom.com.  I recommend that for two reasons.  First, I was never able to get much help from any of the myriad of Adobe Forums in trying to discuss the concepts of modularization as they apply to an AIR application.  There was that lengthy white paper for Flex, but trying to get specific help on code-level implementations was not successful.  Second, since what I think I may know about the topic is so apt to be wrong, it would be better just to confuse you rather than everyone!
That said, for some perspective, in my mind the topic of RSL loading covers two closely related matters.  One has to do with the RSL support for the various Open Source frameworks.  While I was wrestling with trying to manage which versions of which SWZ and/or which SWC would be needed by various sub-applications, I asked why in the world we had to do this anyway.  So, I am happy to see -- but have not yet tried to re-engineer my solutions -- that Adobe has agreed to host those RSL files rather than asking each of us to do it.
The other RSL -- my frame of reference, maybe not yours -- topic is the managment of your own modular application code.  I finally ended up with an application manifest file that could be used to determine the current release level of each 'module' and each 'SWC/SWZ' installed on the users desktop.  Then I could make a quick check of the current release level available on the server, and push out only whatever library needed to be refreshed.  If nothing needed to be refreshed, the load was just local, otherwise it was downloaded, inserted into the user's file system and then loaded on demand, only if the user was working in some part of the application for which that library was required.  If the user was not working with that sub-application, he would not see the overhead of checking for or installing the updated library code.
So, if those are things on your mind, maybe I can help, but since the Adobe developers seem to have a much different perspective on the dangers of loading code into a desktop or web-centric application, I am pretty sure that what was working for me 10 months ago will not work with the Flex 4.1, AIR 2.0.2, and I will once again be looking for some white paper where someone tries to explain all the reasons for all those sandbox bridges.