Air is client side. ColdFusion is server side. In the sane way your web browser does not parse ColdFusion, neither do AIR apps. They are front-end/client only. Think of an AIR app as an AJAX/DHTML web page, or a Flex-built flash application. Both of those operate in a browser and are independent of any server-side language. AIR is the same thing, but it is precompiled as a stand-alone executable on the users pc. It has the same interaction with ColdFusion (or PHP, or ASP, or JSP) as a web page would-- through web service calls.
The only connection HTML or Flash would have in the context of a web page, is that the HTML/swf is requested from the server and CF might have controlled what HTML or swf the server returned. AIR apps don't request their pages from the server-- they are predetermined and compiled into the app, AIR simply populates the interfaces it has with data retrieved via it's web service calls. Hope that helps. ~Brad -----Original Message----- From: Scott Stewart [mailto:[EMAIL PROTECTED] Sent: Friday, December 14, 2007 9:52 AM To: CF-Talk Subject: RE: To AIR or not to AIR? Meaning that the purpose behind AIR is to make portable Desktop apps out of web apps (as I understand it, from my brief research). When you do this don't you negate any built in ColdFusion functionality. Or have they built a ColdFusion parser into AIR? Color me confused but curious ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:294805 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
