It's limiting to have to choose between uploading a swf OR creating dynamic embed code.  I'd like to be able to make XML REST API calls directly from flash, but I'd also like to generate dynamic embed code.  If I refer to a swf that lives in my domain, I can't make XML REST API calls from flash because of the myspace crossdomain.xml file.  If I upload a swf, I lose the ability to generate DHTML to add dynamic HTML, multiple SWFs, etc.

Is there a way to refer to my swf (using a cache server perhaps) on a myspace URL but load the swf dynamically from embed code that I generate not myspace?

To MSP development team: What would also be ideal is to allow SWF in HTML via a special embed. This will allow you to have a single set of code to run in all surfaces. For example, if you only have one large SWF for the canvas, you could detect the surface and generate informative messages on the profile and home views. This precludes having to write 2 versions of Flash for large and small surfaces.

Mark

I had some luck testing using 2 applications, one to host the SWF and the other to be the public facing app. I grabbed the URL of the SWF app, on the MS cache server, from the canvas view and embedded it in the HTML/JS app. Seemed to work fine, but anytime you update the SWF you get a new URL so that parts a little fragile. Also, don't know if the cache path is subject to change on the Myspace end or if this is breaking the TOS somehow. Then there's the whole international cache issues that seem to be causing problems.

If nothing else it's a proof of concept that it's a workable solution.

~Brock