This article could end up being a complete waste of space, as I am operating under more real-world re-interpretation of the raison d'ĂȘtre of
<cfclient>
, as described by Ram:ColdFusion [11] has added support for client side CFML (<cfclient>) and this code is translated to JavaScriptMike Henke has pointed out that the first part of this "CF11 has added support for client-side CFML" is actually bullshit (my wording, not his):
"ColdFusion Splendor has added support for client side CFML" is probably phrased wrong and gave me flash backs to VBScript or CFML running in the client browser.Because... there's not such thing as "client-side CFML". That would imply CFML actually running on the client (ie: the browser, or the mobile device, as is the target of
Maybe this is better verbiage. "ColdFusion Splendor has added support for CFML to generate JS".
<cfclient>
as a concept). This is absolutely not true. I know Ram went on to qualify what he meant there, but the messaging from Adobe on <cfclient>
has been inaccurate. Possibly I think to the point of actual misrepresentation (in the legal sense, I mean).What
<cfclient>
does is... convert CFML code to JavaScript. So let's look at that idea.