Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What’s the difference in terms of security between declarative and programmatic SWFLoaders? In the ff. code, loader1 throws a security exception while loader2 does not.
public someFunction(source:String):void { var loader1:SWFLoader = new SWFLoader(); loader1.load(source); loader2.source = source; } ... <mx:SWFLoader id='loader2'/>
I don’t think there is any difference in terms of security. Remember, MXML gets converted to ActionScript by the mxmlc compiler before the actual compilation commences, so a declarative SWFLoader (or any other declarative element, for that matter) is just a short-hand way of creating something instead of coding it by hand. You can use the
-compiler.keep-generated-actionscriptmxmlc argument to see what kind of code gets generated from your MXML.And the reason you’re not seeing a runtime error from the
loader2.source = source;line in that example is that since the previous line of code invokes an error, the execution of that function stops there. Try commenting out the line where you callloader1.load(source)and you’ll see the next line throw this kind of a SecurityError: