Ironically upon reluctantly plunging back online today in a quest for VO understanding I came across this post: http://www.advantexllc.com/blog/post.cfm/how-oo-almost-destroyed-my-business
Now let me first SHOUT a sincere thankyou to all community members who contribute their expertise to these forums. Second I want to stress my frustration is similar to the above poster in the "requirement" to "learn" so extensively at the expense of "getting things done".
That said, even my limited experience in HTML revealed the need of big apps such as the one I am attempting to have an "architecture".
So, rather than continuing to understand VOs as a building block toward implementing an architecture I've decided to tepidly take on one of Cairngorm/MVC/Swiz -- actually Mate is the "leader" after the first hour of reading fwiw.
Yet (in no small part because the decision above could be a blind alley) I would appreciate continued feedback on a few "conclusions" I set out below (hopefully) for the benefit of future readers.
1.) MVC needs to be understood in the context that all three building blocks of a web app (Database -- WebServer/CF -- Frontend/Flex) might each contain some of all three "MVC aspects" (ie model exists both on View and obviously at dbase). Hence for example a CF architecture like cfonwheels is potentially both supplementary to and redundant to a flex architecture. Similar assertions apply to my intention to push (some) business logic past from CF into MySql Stored Procedures. For better or worse though, many existing architectures focus solely on their "layer" (DB/WebServer/View).
2.) Implementing any architecture infers learning and then working with a great deal of other peoples sometimes poorly documented code. Yet this to an extent is not that different from using say MXML -- which I probably am semantically wrong to say but is arguably an "architecture" itself. Regardless, architectures add overhead to non-large apps (presumably there is an economy of scale effect).
3.) Boiling everything down, the need is to manage DBase <--> View interactions. JSP/CF can assign properties to DB elements which Flex/AS can "map" to for increased efficiencies. Cost/Benefit of CF included, are JSP a more "programmically straightforward" option??
As always, thanks in advance.