Hi, > The only advantage to un-signed RSLs is if you serve more than one SWF that > uses them from your domain. SWFs end up on disk in a browser cache (if > there is one and within the limitations of that cache) so then there is a > probability you won't have to download some code. Which is also an advantage if a user visits a single application more than once.
> Apache Flex will hopefully release often. The Framework RSLs were > version-specific, so releasing often further lowers your chances of any > benefit even if we did have a way to serve cross-domain RSLs. Even if we release more often users are likely to visit a given site more often than we make releases. If we released monthly and a user visited a site every day that's 29 times that user didn't need to download the RSLs (assuming they stayed in the browser cache for that long). > I suppose we could try to host RSLs at some known place Other than a cross domain policy what else would this require? I lot of JS libraries do the same thing so it may be worth investigating. eg google hosted libraries at https://developers.google.com/speed/libraries/ Thanks, Justin
