Believe me we've thought about it.  In the end we decided that adding
the support into the Player to download and cache some libraries that
were only from Adobe (because there ended up being huge security holes
if we allowed 3rd party caching) wasn't going to provide enough value to
first-time users to warrant us undertaking it at this time.  Doesn't
mean the idea is dead, it continues to be something we think about.

Matt

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Brian Lesser
Sent: Tuesday, April 25, 2006 7:56 PM
To: [email protected]
Subject: [flexcoders] Component Framework RSL cached by the player - is
that reasonable?

Hi,
After Sho's talk at FITC, I've been thinking a little more about runtime

shared libraries. They are a great idea but the first time someone loads

something from a site they have to download each RSL. If they visit
different sites that use Flex they will be forced to download much of
the same component framework each time. In other words users will be
downloading a lot of duplicate code over and over and over again. Each
time they do that they will watch the progress bar. Not a good
experience.

In a post after MIX 06 Branden Hall mentions that the WPF/E plugin will
have a limited set of components baked into the plugin:

http://www.waxpraxis.org/article/2/we-finally-see-the-flash-killer-from-
microsoft

It makes me wonder how MS plans to update those components/containers?

But the idea has some merit. Now, let's say that the Flash 9 (or Flash
10) player could download from Adobe and cache each release of the
component framework as an RSL. If there was a compiler setting you could

use to tell the compiler: "get version 1.2.2 of the framework from
adobe.com" you would be set. When your SWF loaded the player would check

its cache to see if it already had the framework 1.2.2 RSL. If not it
would get it from Adobe. The next time someone needed that version of
the framework. The user wouldn't have to wait for it to load.

Does that make sense? It's obviously too close to Flex 2's release to
seriously request it version 2.0, but maybe it is reasonable to propose
it for a later release?

I'm curious if people think a scheme like that is workable and
beneficial. My apologies if this has already been discussed or is
obviously stupid.

Yours truly,
-Brian

--
______________________________________________________________________
Brian Lesser
Assistant Director, Teaching and Technology Support
Computing and Communications Services
Ryerson University
350 Victoria St.
Toronto, Ontario                   Phone: (416) 979-5000 ext. 6835
M5B 2K3                            Fax: (416) 979-5220
Office: AB48D                      E-mail: [EMAIL PROTECTED]
(Enter through LB66)               Web: http://www.ryerson.ca/~blesser
______________________________________________________________________



--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives:
http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links








--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




YAHOO! GROUPS LINKS




Reply via email to