> > > C. This brings us back to the question... what makes this a good idea? Why > overly complicate something?
While it may not be common, there are a lot of large organizations out there with multiple applications in multiple languages. Having a tool that can integrate these applications can be very powerful. Getting a couple of developers up to speed on CF to write some "glue" code to get, say a .NET app and a PHP app talking to one another may make more sense than completely porting applications to another language. This isn't just an abstract scenario - this is a potential solution to a real world situation I was in a year or so ago - two large (50+) development teams combined - one team was .NET, one was Java, and they wanted to create a system that could leverage apps from both teams. The "solution", at the time, was to choose .NET as the standard, and port all of the Java code. Ick. Now with CF8's .NET support, one or two developers could simply have created the "bridge" app, and the rest of the developers could have continued moving forward with either Java or .NET or both. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:280117 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
