No. An RSL is used to inject code into an application domain, usually the main apps AppDom. If both appA and appB share a bunch of classes, those classes go into an RSL shrinking the SWF size for appA and appB. If appA loads first, it does an additional server fetch to get the RSL which takes extra time, but when app B loads, the RSL is hopefully still in the browser cache, saving the appB from downloading those same bytes.
If appA loads moduleC, moduleC normally loads into a child appDom so it can be unloaded. moduleC is generally built with -load-externs for any classes it can expect from the parent, and that set will be the same whether appA loads some of its classes from an RSL or not. moduleC should not try to load an RSL at all since those classes are already in appA's appDom at the time moduleC gets loaded. If moduleD and moduleC share classes, those should not go into an RSL either since they would be loaded into sibling appDoms effectively loading the code twice. That's where the shared code module technique comes in (see my blog). The principle is to load a class once, and only when needed, and cache things when you can. Once you understand your appdom topologies, you can start to see where to use RSLs and where to use shared code modules, which are effectively late-loaded RSLs. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Schultheiss Sent: Wednesday, April 02, 2008 4:44 PM To: [email protected] Subject: [flexcoders] RSL vs External SWC Hey, It's suggested to only use RSL's where multiple applications will use the same RSL. Does an application with modules qualify for RSL's? With module applications are RSL's preferred or library SWC's with external links?
