
BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 15
4 .NET Features Requiring No Change in CFML Code
There are some features of the .NET Framework which provide benefit to CFML developers
even if they don’t change any of their CFML code. New Atlanta believes that .NET simply pro-
vides a better platform for CFML execution. This section discusses some of the features.
4.1 .NET Framework Features That CFML Pages Inherit
There are several features that the .NET framework enables which normally are discussed only
with respect to processing ASP.NET pages. Since BlueDragon.NET enables CFML pages to be
processed similarly to ASP.NET pages, these features and benefits are available (or can be con-
figured to apply) to CFML pages as well.
These features require no changes to the CFML pages and instead are configured in IIS or the
.NET framework by way of XML entries defined in the standard .NET configuration file,
web.config. See section 6.3 and following for more on the location and purpose of this file and
how to edit it.
Following are some of the features that can be enabled in the .NET framework to benefit all
pages, including CFML pages:
• Queries in CFML are processed using ADO.NET, which offers both enhanced perfor-
mance and added features over JDBC-based processing
o As described in section 4.2, database processing in BlueDragon leverages Micro-
soft’s ADO.NET drivers for all database processing. Besides the benefits of Mi-
crosoft’s native support and performance, among the features that can be leve-
raged is use of ADO.NET connection pooling, as discussed in that section 4.2. No
CFML code changes are required to leverage this benefit.
• Web services in CFML are served as native .NET web services, offering enhanced
functionality over java-based web services
o See section 4.3 for more information
• Leveraging .NET Clustering, Load-Balancing, and Fail-over
o Because CFML runs in the same pipeline as ASP.NET, any available mechanisms
(from Microsoft or third parties) to enable clustering, load-balancing, and fail-
over will accrue to the benefit of CFML developers
o Further, because CFML session variables are integrated with ASP.NET session
variables (next bullet), mechanisms available to persist sessions to database or
other shared datastores enable clustering without requiring “sticky sessions”
• Leveraging .NET Session Variable Persistence for Clustering
o It is possible to configure web applications in the .NET framework so that session
variables are stored not just in memory but also in a database or a state server (a
Comentarios a estos manuales