1. You should use air if you want it to be standalone.
2. A published air file can be downloaded and installed automatically.
3. You can even add update functionality. When a user starts the application which is already on his computer and you have uploaded an update, the client automatically shows an update screen! (very cool!)
4. In air you can use mySqlLite which makes it possible to embed your database in the application, no online link required
5. You can use coldFusion but also mySql. If you choose Flex/PHP/mySql, you should consider working with AMFPHP which is an easy to learn and very powerful technology! http://www.sephiroth.it/tutorials/flashPHP/flex_remoteobject/
6. I don't know if air applications are that hack safe. Flash player doesn't have a good reputation on that part
Hope this helps a bit
Thanks for the quick response. To continue the discussion,
when you say the coldFusion is touted by Adobe heavily, what exactly do you mean?
I'll draw a simple sketch of how i think i want the system to be :-
- Standalone application with an embedded database support.
- The Business logic layer should not be decompilable, which probably means it should not be a flash component. Yet i want the whole system to be ready thru just one installation,i.e, the AIR application installation.
- Oh and also, i found out something about BlazeDS, and i was thinking whether i could use that as a layer above the database and since its java its going to be hackproof. What i need to know is whether i can actually install everything in just one go when i install the final application!
Thanks In Advance
If your're going to implement ColdFusion, BlazeDS and embedded databases, I can't help you further because I'm a Flex/PHP/mySql developer with no experience in ColdFusion and BlazeDS. I suggest you split up your questions and post them seperately. There are several people on this forum which will be able to help you on specific topics.
Ok, removing the terms ColdFusion and BlazeDS, how would you achieve the system i've written it? assuming theres a non decompilable database layer...