If the SWF is really big, it could still take time to get all the bytes loaded and you'll see "Loading" if that takes a while.
Regardless of the size of the SWF and whether it is cached or not, if it takes a while getting all of its objects created in order to run, you'll see "initializing" during that time. Most Flex apps will show "initializing".
RSLs will not make a difference once the SWF is cached. It will only shorten the time Loading appears during first download.
Flex SDK Developer
Adobe Systems Inc.
Thanks for getting back. But would like to get my doubt cleared a bit more.
This link has a mention of "loading" for the downloading phase.
This is where Iam puzzled. If the swf is cached by the browser and if the user clicks on the same
page again(containing chart components), why does the "loading" message come up again.
Since the file cannot be downloaded again, one would assume that atleast only "initializing"
message is seen. But this is not the case
Please clarify. I would like to understand the difference if any b/w downloading and loading phase.
(esp in the context of caching)
Also, theres one observation:
I am testing with IE 7, FF3, opera.
Ie7 : second time - preloaderd doesnt even comeup.
FF3 : Loading + initialization message ALWAYS comes
Opera : Only initialization message comes (atleast from second time)
swf as mentioned is being cached (headers being sent out are cache_control, expires.