This really is not effective. Ultimately the swf still ends up getting
sent to the client when the application is used. Then that user can get
the swf out of thier cache and decompile it to grab the assets. As Tom
explained, If your app loads external swf's you cannot protect them, you
can only make them a little more difficult to access.
-Steve
-----------------------------------------------
Naz wrote:
Yo. Adding scripts that do the following to each of your map content
swfs should solve your problem: 1) Create an if-then statement that
checks for a variable that your map loader swf will set. If this
variable is not set to the proper value that your loader/viewer swf
sets, make the map swf do sometjing ugly like turn invisible or
something ;-P (._alpha=0;) *oh, set these variables to something else
when the map .swf first loads, then have them communicate and request
for the proper value from the loader swf upon completion of loading.
This is so people who've decrypted the urls can't enter
"http://yourdomain.com/mapName.swf?variableToCheck=properValue";
<http://yourdomain.com/mapName.swf?variableToCheck=properValue%22>
manually in the browser's url field. 2) Have each map .swf check whether
it is loading from the proper url. If not, disable displaying it.
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
