[osflash] Why Flash?
marc.hughes at gmail.com
Sat Jan 13 10:30:27 EST 2007
Wallop does something like that.
Then the child swf can allowDomain() the main swf, and the main swf
sticks an object into the child swf that can be used for
communication. I haven't tried it, but it seems like it should work.
On 1/12/07, David Rorex <drorex at gmail.com> wrote:
> On 1/12/07, Steve Polk <nospam at webpolk.com> wrote:
> > I mean, you can upload your very own SWF into our engine to be displayed
> in a controlled popup. This will allow people with animations, games, etc to
> join in the fun. The server scans the SWF for the size and builds the HTML
> wrapper to open the Flash content appropriately.
> > I felt allowing the SWF to be inside the engine, like wallop does, would
> be too risky exposing some of the internal architecture to 3rd party
> developers. This could be nice for some, being able to reuse some of the
> existing data/framework. However, the risk of getting someone on with some
> knowledge and a little reverse engineering could wreak some major havoc on
> the DB!
> Something like this should in theory be solvable by taking advantage of
> Flash's native cross-domain protection. Put all the user-uploaded SWFs on a
> separate domain, and then they will not be able to access/communicate with
> the parent SWF at all. The only issue is when you DO want some limited form
> of communication, I'm not sure how you'd do that. It's either all on, or all
> -David R
> osflash mailing list
> osflash at osflash.org
More information about the osflash