Our RSL's are from the SDK we are actively using. Then we use custom flex-config files to add the "runtime-shared-library-path" nodes for the RSLs. This allows us to declare where on our servers the RSLs are. The 4.6 Adobe signed ones use a custom cache for flash that doesn't easily get wiped out. The new ones you make will end up in the users browser cache. Since all of our applications are on the same domain, we can have them share the cached RSLs.
Not sure how to go about trying to get it into the local store and then reference it later. The application would be still trying to reference it from the server and the client browser would just offer it up out of the browser cache. On a side note, I haven't tried yet, but would love to host the RSLs from a separate server in the domain to balance out the network load a little. -Mark -----Original Message----- From: David Coleman [mailto:david_coleman_...@hotmail.com] Sent: Monday, December 02, 2013 1:14 PM To: dev@flex.apache.org Subject: RE: SharedLibrary not works with SDK 4.11 Having not tried this solution myself, this is pure speculation... but couldn't local storage store this? set domain to be "*" and retrieve it from the public svn repo. if not present the RSL manager can load it up and in this way we can sign it with our own Cert and validate that cert independent of Adobe? Would this be workable? I've used local storage only for single sites before... but wouldn't it be possible to massage local storage to store something "global", like rsls? Or in your case, Mark, you could maybe do something similar at the application level, storing them at least for your own set of applications under a base domain... RSL's are the only reason that I hesitate to migrate our Facebook app to apache. it will kill our CDN.
