Our application is a bit slow to load at startup, i’m wandering myself if a sepation of the module of the application in several swc will decrease the loading time( grosso modo : a module = a “page” )
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Our application is a bit slow to load at startup, i’m wandering myself if a sepation of the module of the application in several swc will decrease the loading time( grosso modo : a module = a “page” )
SWC is simply a compressed zip-like archive of classes (static library)/
Compiling an application against SWC doesn’t change the outputted swf.
There are 2 means by which you can decrease the initial loading:
1.RSL – dynamic library which are loaded separately from the application and can be cached.
Any RSL signed by Adobe can be cached not just by the web browser which is platform-dependent caching, but also by the flash player itself, which means that even if a user clean its browser cached or has no cache at all, once the RSL is downloaded, it’s cached.
This is typically useful for runtime loading of the flex framework & the RPC.
The other type of RSL caching like said earlier is browser caching.
Either way, RSL is loaded at startup.
2.The other way is by extracting parts of the application into modules, which will be loaded by demand. For example, if the application has 3 screen, each screen will probably be loaded [“probably”, because it’s up the developer to decide when] only when the user first enters this screen