On 11/5/14, 11:22 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> First step is to contact the third-parties and find out how they want to >> get loaded (import or sandboxed with Marshall Plan). > >It would be useful if you included links to these techniques (to save >people time) as not everyone may know what is required here. OK, wasn’t sure folks wanted a tutorial on third-party content. Didn’t think a lot of folks needed to know, but here goes: “import loading” is defined here [1]. Yes it is in the loadBytes() method but applies to regular loads as well. I’m told it is equivalent to wget [2]. The content is effectively copied from the third-party server to the TDF server. This can break the third-party content if it relies on having the third-party domain name in the url or in HTTP headers. The Marshall Plan [3] was the nickname for multi-version support in Flex [4][5] that also solved communicating between sandboxed applications. Data is marshaled across the sandbox boundary. Both the loading app and the loaded app need additional code to communicate. Because nearly everything is sandboxed, there is less room for security issues, and third-party content doesn’t have the issues it does when import loaded. HTH, -Alex [1] http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/di splay/Loader.html [2] http://en.wikipedia.org/wiki/Wget [3] http://blogs.adobe.com/aharui/2008/08/marshall_plan_at_360flex_confe.html [4] http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084 -7f0c.html [5] http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf619ab -7fe2.html
