Wow! This list just keeps getting longer. I've noticed that a lot of the additions you all want are design based. Here's a few fundamentals that'll open Flash up to new things:
1] Proper reference passing to scripts
I have foind that it is *extremely* unreliable trying to get the URL of the refering page through the HTTP_REFERER environment variable with server-side scripts. This has already caused problems for at least one Flasher who has written a game and someone faked the high-score by submitting bogus data through a HTML page. Because we can't get at the referer information we can't check where the data has come from and therefore ensure its authenticity!
2] Optional Code Protect on ActionScript
Open Source code is great and allows people to learn but... the above problem could have been solved by implementing rudamentary encryption in AS before sending the data to the ASP. However, given that any old blighter can get their hands on an AS viewer it would only require that they receate the code in order to falsify the data. If we had code protection this wouldn't be a problem.
A knock-on effect of CP on AS would likely be more processor load while the Flash plug-in/player decrypted the AS before executing it but for those of us who need CP this would be a welcome [and optional] addition!
Regards,
Steve
