Hi Dave, would you be willing to share any information as to exactly how you've divided the functionality between the items described below.
>Another way to identify what goes where is to follow the natural >MVC boundaries: Model = Java, View = CF, Controller = either, but >probably CF. IMHO, that allows each language to play to its >strengths. I followed this division of labor in a Mach-II app and >it worked great. But as Denny pointed out, it might not be so >great for the client. The next developer that picks up the app >will need to know both CF and Java. > >Dave Jones >NetEffect ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:251464 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
