On Thu, Apr 28, 2011 at 9:49 AM, Christofer Dutz <[email protected]> wrote: > Ok .. just had a look at this caching thing ... have to admit that I > haven't used it before ... but what I just saw certainly looks like I > should have a look at it ;-) >
So, this is the way I understand it. You can use RSLs a number of different ways. a) Framework RSLs - unsigned, meaning you deploy these as swcs on your web server and the client SWF will download them and cache them in the app cache space b) Framework RSLs - signed, meaning they must come from the Adobe URL - they are signed by Adobe and if the FP resolves them, they will be cached in the player's cache space, and can be re-used by any app that makes use of them c) Your own libraries as RSLs - I haven't bothered with this yet, we link all swcs we create directly into our SWFs (for now) If you spec signed RSLs, then you can copy a backup to your webapp, in the event that Adobe isn't available at runtime to resolve them. This is just good practice. So, in flexmojos, the way you spec this is in the configuration...like here: https://docs.sonatype.org/display/FLEXMOJOS/Runtime+Shared+Libraries ..but that wiki isn't 100% correct. You need to spec the <rslUrls> indeed, but you also must spec a dependency on each of the framework libraries, and spec the <scope>caching</scope> Apparently, you also have to spec the dependencies in the same exact order that they appear in $FLEX_SDK_HOME/framework/flex-config.xml Now, if you run the goal copy-flex-resources, by default it will try to copy the swz dependencies to your webapp's dir (that you specify). This also confuses me a bit, since it was my understand that .swz files may *only* be downloaded from Adobe at runtime. I could be wrong on this. If so, I guess the .swz files in your local webapp serve as the backups. I was thinking that it would instead try to copy the .swc files to your local webapp as a backup. However, the textLayout causes all sorts of headaches. Since this library was seemingly re-named to be version 4.1 (but it is really version 1.1), then copy-flex-mojos fails trying to copy the 4.1. swz file over to the webapp. Hence, my question / dilemma. I guess to get around this problem, I can deploy the textLayout 1.1 to my local repo as textLayout 4.1 swz, but I want to know if they are supposed to be binary compatible. -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
