It's just off the top of my head (and I probably gave it the wrong name - there's no encryption involved) - You could perhaps do something like a client/server exchange when the app starts up to agree some sort of 'handshake' code; and when you request each mp3 use that code. Have the code expire when the app closes or the session expires.
The only other thing I'd suggest is to move away from straight mp3 files and use streaming - Red5 or similar. Then there's no chance of the user downloading anything directly. Sorry - can't think of anything over and above that. Why no renaming? Even if the MP3s are used by another client or something, at the very least you could put in an alias (mod_rewrite, for example) and use the aliases from Flash. Ian On 11/9/06, Gadlin, Steve <[EMAIL PROTECTED]> wrote:
Renaming isn't an option here... Can you explain more about this one time key encryption? Steve
_______________________________________________ [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
