On 9/23/14 1:56 PM, "Frédéric THOMAS" <[email protected]> wrote:
>> Essentially, this trick makes remote content local. It can make remote >> calls, but the headers will be the same as if you coded URLLoader in the >> main AIR app not as if it was a web-app served by the domain's server. > >If it means the loaded swf is perceived as or is in the local application >sandbox / security context, I guess it can do the trick moving the rest >of the code in a module downloaded by the loaded swf, thought ? AIUI, you can keep "importing" swfs into the application sandbox, but the servers that they came from will not see the same headers as if it was a web app from that server and will respond differently, often by returning failure. If you download remote.swf and load bytes it, and it just uses Loader to run anotherremote.swf, anotherremote.swf is loaded into a sandbox and cannot access the remote.swf. Remote.swf would also have to use the load bytes trick in order for anotherremote.swf to talk directly to each other. -Alex
