I agree with Daniel's original characterization. To clarify:
Some operations that might occur in the view layer: -skinning/templating -parsing input -formatting output based on output received from the Controller
All those operations can be done with CF, with plain HTML as just the very outermost interface to the user. I suppose it boils down to semantics, but your presentation layer does not have to be strictly client-side. As far as I'm concerned, the functionality I listed above belongs in the View, not the Controller, and I can do those things much easier server-side than client-side.
Your Controller (CF or your CF-based framework of choice) takes parsed inputs received from the view layer (CF) and initiates actions on the Model (java) based on those inputs.
You have the best of both worlds: your model gets to exist in the abstract world of objects (where java works well); your controller and view get to use CF where CF's ease of use pays off.
Conan
At 09:55 PM 9/22/2004, you wrote:
Daniel,
I am not following you with this implementation of the MVC Design Pattern. ColdFusion is not a Presentation Server by any means. CF and JAVA can work hand in hand to implement MVC but I am not sure why you describe CF as handling ANY presentation at all. Your presentation layer is handled through FLASH MX or HTML. You can use CFC's and or Java servlets to handle your Controller and Model Layers, but CF and JAVA are server based programming languages.
With CF, we architect solutions to separate the CF from ANY Front End functionality, albeit it does have the capabilities of rendering graph's, etc.
Any how, I look forward to any response because I am curious as to how you came up with this concept of CF as a Presentation server.
Thanks in advance
----------------------------------------------------------
To post, send email to [EMAIL PROTECTED]
To unsubscribe: http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe: http://www.dfwcfug.org/form_MemberRegistration.cfm
