June 8, 2007 at 10:29Flex 3: Radically small SWF file size (continued)
Continuing the previous post , we will try to examine in more detail the mechanisms for reducing the size of the output SWF files of Flex projects:
Cross-Domain: The
cache of the Flash player allows the Flex framework to be cached for cross-domain use. The end user just needs to visit one of the sites where he downloads the Flex Framework (Flex 3.0.0 Moxie) and caches it. And now, when visiting other sites that use this framework, he takes it from the player’s cache.
Version support: The
player’s 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 problem, a code signing mechanism has been added to the Flash player, and the code must be signed by Adobe. In light of the fact that 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.
Failover and hosting:
Flex framework can be located anywhere, even in several places. And they are completely independent of the Adobe domain or any other. This feature includes support for fallback URLs so that the Flex framework can be found in several places. If a simple server happens on one server, the application will download the framework library from backup (feyloverny) URLs.
Cross-domain RSL (Runtime Shared Libraries): The
Flex framework now supports RSL downloaded from other domains. For example, Yahoo provides a library of all Yahoo stuff using Flex 3. They can decide that any team can load the library and allow code reuse across Yahoo domains.
Well, that seems to be all ... Ted intrigues us more and more. He says that in “The Light Star”;) (FrogStar) a lot more awaits us ... but for now he creates a veil of mystery :) Well, that’s right. Will wait.
Cross-Domain: The
cache of the Flash player allows the Flex framework to be cached for cross-domain use. The end user just needs to visit one of the sites where he downloads the Flex Framework (Flex 3.0.0 Moxie) and caches it. And now, when visiting other sites that use this framework, he takes it from the player’s cache.
Version support: The
player’s 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 problem, a code signing mechanism has been added to the Flash player, and the code must be signed by Adobe. In light of the fact that 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.
Failover and hosting:
Flex framework can be located anywhere, even in several places. And they are completely independent of the Adobe domain or any other. This feature includes support for fallback URLs so that the Flex framework can be found in several places. If a simple server happens on one server, the application will download the framework library from backup (feyloverny) URLs.
Cross-domain RSL (Runtime Shared Libraries): The
Flex framework now supports RSL downloaded from other domains. For example, Yahoo provides a library of all Yahoo stuff using Flex 3. They can decide that any team can load the library and allow code reuse across Yahoo domains.
Well, that seems to be all ... Ted intrigues us more and more. He says that in “The Light Star”;) (FrogStar) a lot more awaits us ... but for now he creates a veil of mystery :) Well, that’s right. Will wait.