I guess I could sort of buy this, but I would still think of this as "CF tags exposed as services" in the case of their exposure as remote services. I would also consider calling them in CFSCRIPT as calling them as objects, not really as CFCs.
I tend to look at CFCs as code a developer writes. CF9 exposing some tags as services or objects are just that, exposure as services and objects. It doesn't *make* them CFCs, though they do behave in similar ways to CFCs. At the end of the day though, I could care less what people call them. I would probably not call them CFCs myself. -Cameron On Mon, Feb 8, 2010 at 4:04 PM, Judah McAuley <[email protected]> wrote: > I believe that this actually has changed as of CF9. > > The built in service tags (cfmail, cfhttp, cfpdf, cfftp, etc) in CF9 > are now exposed in cfscript as objects. > > So if you want to do a form post using cfscript, you would do something like > so: > > myconn = new Http(); > myconn.url = 'http://google.com/' > > Since you are able to use the new keyword, instantiate an object and > then dump that object, I'd say that all the service tags are now > built-in CFCs in CF9. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:311867 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
