Structuring System Architecture in a Flex Web Application on a Budget (w/o Java)
- by phwd
I started a project a while back using the following architecture from Adobe Developer Article talking about Creating marketing platforms in Flex. I did my first set of coding locally forgetting that my server did not handle Tomcat. So I said okay, and cut some corners and then some other limitation came up and I cut some more corners. Eventually for a good week or two, it was trying to get the project working with making the ends meet. Layers started to merge.
In the end I used a
PureMVC (Presentation/Client) - ZendAMF (Communication) - MySql (Data) Layout.
It worked but I never felt as though I had some layer just to take care of all the SQL calls to the data.It just felt hacked together
So should I keep the above setup and just start from the presentation layer and move downwards like they said in the article or is there a better layering (based on a hosting plan that does not handle Java) I could accomplish ?
NOTE: I would just ask the adobe guys but they barely reply on their site.
Thanks !
