My option is 5.
Normally I load it as needed.
And if it is predictable, then I consider to preload it in case it is
somewhat heavy content.
HTH
Cor
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of allandt
Have a look at Gaia framework for some ideas.
Previously, I have loaded a sitemap XML and then loaded SWF's for pages
on request.
On another site which had quite a lot of animations and videos, I
implemented an intelligent preloader that would look for assets in the
sitemap and load these
I agree with Glenn... it depends on size, particular example and is
often a speculation before the project starts running. If this is
going to be a micro-engine, why not add a set of modes and use one
depending on site. However this would mean a lot of work and testing.
Perhaps a more elastic
Another factor to consider is the client's willingness to pay for bandwidth.
(Assuming you have a client.) If they need to keep costs down then you
probably should avoid preloading content that the user would need to drill
down to, since the user may never see it.
--
4 matches
Mail list logo
