Flex 3: Radically small size of SWF files (continued)
Continuing the previous post , we will try to consider in more detail the mechanisms for reducing the size of output SWF files of Flex projects:
Cross-Domain:
Flash Player Cache allows the Flex framework to be cached for cross-domain use. The end user only needs to visit one of the sites where he loads the Flex Framework (Flex 3.0.0 Moxie) and caches it. And now, when visiting other sites that use this framework, it takes it from the Player cache.
Version support:
Player Cache supports Flex 3.0 and future versions of the Flex framework. When creating a Flex application, you can choose which version of the framework to use.
')
Security:
Cross domain caching opens up many security issues. To fix this, a code signing mechanism was added to the Flash player, and the code must be signed by Adobe. In light of the fact that with Flex 3 is going to become Open Source , developers will be able to get new features and components added to the Flex framework, provided that they meet the security requirements.
Fileserver and hosting:
Flex framework can be located anywhere, even in several places. And they are completely independent of the domain of Adobe or any other. This feature includes support for backup URLs, so the Flex framework can be found in several places. If a single server happens to be idle, the application will download the framework library from backup (file) URLs.
Cross Domain RSL (Runtime Shared Libraries):
Flex framework now supports RSLs loaded from other domains. For example, Yahoo provide a library of all Yahoo stuff using Flex 3. They can decide that any team can load the library, allow code reuse through Yahoo domains.
Well, everything seems to be ... Ted intrigues us more and more. He says that in “The Flying Star”;) (FrogStar) we still have a lot to expect ... but for now he is creating a veil of mystery :) Well, that's right. Will wait.
Cross-Domain:
Flash Player Cache allows the Flex framework to be cached for cross-domain use. The end user only needs to visit one of the sites where he loads the Flex Framework (Flex 3.0.0 Moxie) and caches it. And now, when visiting other sites that use this framework, it takes it from the Player cache.
Version support:
Player Cache supports Flex 3.0 and future versions of the Flex framework. When creating a Flex application, you can choose which version of the framework to use.
')
Security:
Cross domain caching opens up many security issues. To fix this, a code signing mechanism was added to the Flash player, and the code must be signed by Adobe. In light of the fact that with Flex 3 is going to become Open Source , developers will be able to get new features and components added to the Flex framework, provided that they meet the security requirements.
Fileserver and hosting:
Flex framework can be located anywhere, even in several places. And they are completely independent of the domain of Adobe or any other. This feature includes support for backup URLs, so the Flex framework can be found in several places. If a single server happens to be idle, the application will download the framework library from backup (file) URLs.
Cross Domain RSL (Runtime Shared Libraries):
Flex framework now supports RSLs loaded from other domains. For example, Yahoo provide a library of all Yahoo stuff using Flex 3. They can decide that any team can load the library, allow code reuse through Yahoo domains.
Well, everything seems to be ... Ted intrigues us more and more. He says that in “The Flying Star”;) (FrogStar) we still have a lot to expect ... but for now he is creating a veil of mystery :) Well, that's right. Will wait.
Source: https://habr.com/ru/post/9650/
All Articles