Caching the Framework
Flash Player 9, Update 3 (which is Flash Player 9.0.115) has a feature called Flash Player cache. Flash Player cache isn’t entirely dissimilar from typical browser caching in that it is capable of storing persistent local copies of files and using the local copies instead of remote copies upon subsequent requests. However, Flash Player cache is significantly different from browser cache in two key ways:
Flash Player cache works only with signed runtime shared libraries (must be signed by Adobe).
Flash Player cache works across domains. That means you can download a signed runtime shared library from www.a.com and when an .swf from www.b.com needs that same signed runtime shared library, it will have access to it.
Flash Player cache is a way in which you can dramatically reduce the size of a Flex .swf file. Keep in mind that this does not necessarily mean you’re reducing the number of bytes a user must download to access the application correctly. If the user doesn’t already have the necessary signed runtime shared library files (.swz files) in cache, he will still have to download those. In fact, because the runtime shared libraries are the entire Flex framework instead of only the parts required by the specific application, the total download can potentially be greater than if the framework was statically linked and compiled in the application .swf file. However, if the user does have the required .swz files in cache, all he will have to download is the .swf ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access