1 person found this helpful
The extra swfs that FB4 creates are runtime shared libraries containing all the flex classes - FB4 creates them whether they are needed or not (FB4.5 should remedy that).
The files are cached by Flash Player so they will only be loaded once (when a user visits their first FB4 app). So in most cases, Flash Player will already have all the files cached and only myTest app will need to be downloaded - so loading times should be acceptable.
Also, you dont need to upload them to your server as Flash Player downloads them from the Adobe site not your server.
Take a look here for full details: http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7add.html
big filesize ?
Its just 1 spark list ?! and the main swf is 44kb That should load lightning fast
The main swf may be small, but first load is 2MB because of all of the libraries. Second load is much, much faster because the libraries are cached.
No new user of your app is going to have a 44K download unless they already have the libraries cached.
DO you by any chance have the framework embedded in the swf?
It is funny cause I waited also alot for the load, and I believe I already
already have the libs...
Yes, but these library swfs are coming from the wrong domain to be cached. I guess that's the root of the problem.
I created a second example and only uploaded the main swf:
So the user is forced to download the framework from the adobe site , but try it your self.
Why does adobe do not incude those frameworks into the flashplayer itself ? (Adobe ? please)
2MB is a BIG negative point against using flash based sites especially where some people are claiming that flash is slow...
Is probably the debug version of the flash player not caching ? My player seems not to cache anything at all...
OK, so now anyone that uses a Flex app can now potentially have a fast download because
they may well have a cached version from the adobe site, however your users may or may not be like that on the first run.
Subsequent accesses will be quick.
It's not a Flash issue, so it has nothing to do with the flash player and I don't see a compelling reason for all flash users to have to download these Flex libraries. Flash users typically execute small swfs.
This is simply related to the code used to implement the flex frameworks. The Flex frameworks are BIG. This isn't an issue for enterprise apps - the main target for Flex.
If flash is slow - blame the developer.
>enterprise apps - the main target for Flex.
I think this might change since adobe now have catalyst which is not really targetting enterprise apps.
Why are enterprise apps are allowed to be slow in loading , or do you mean intranet apps ?