
BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 16
service running on the same or another server). If BlueDragon is configured to use
.NET sessions (in the BlueDragon Admin console), then CFML session variables
also benefit from this feature. This gives session variables many of the benefits of
client variables while also enabling clustering of sessions. For more information,
see any discussion of the .NET sessionState directive, such as in:
o Additionally, third party software exists to provide still more scalable, robust
management of .NET sessions, particularly for clustering. ScaleOutSoftware, for
example, has been demonstrated to work with BlueDragon.NET.
http://msdn2.microsoft.com/en-us/library/ms178586
• Leveraging .NET Session Variable Persistence Over Restarts
http://www.scaleoutsoftware.com/
o Related to persistent session variables, another significant benefit of using session
persistence is that they are persisted over server restarts. In traditional ColdFusion
servers, a restart would cause loss of all sessions. With BlueDragon.NET, if per-
sistent sessions are enabled in .NET and ASP.NET sessions are enabled in the
BlueDragon Admin, then sessions are not lost on restart. Existing CFML code
that sets or gets session variables will benefit from this feature, without change.
• Leveraging .NET Application Restart Mechanisms
o When an error occurs in a .NET application domain which causes undesirable
excessive use of resources (too much memory, too many requests, requests taking
too long, etc.), the Framework has built-in limiters set that detect the problem and
try to protect the application. It will create a new instance of the application,
sending new requests to that new instance, and it will quiesce and eventually shut-
down the errant application instance. Since CFML pages run in a .NET applica-
tion domain, the benefit accrues to CFML code. This is discussed further at:
• Multiple Independent Instances
http://samples.gotdotnet.com/quickstart/aspplus/doc/procmodel.aspx
o .NET defines each application (web site, virtual directory, or directory declared in
IIS as an application) to be independent from others—even on the same ma-
chine—with its own administrative settings, website configuration, shared varia-
ble scopes, and more. See section 5.1.1 for more information.
• Multiple BlueDragon Admin Consoles per Web Site, Virtual Directory, and More
o As discussed in section 5.1.1, BlueDragon.NET leverages a feature of .NET
where each web site, virtual directory, and directory declared as an application in
IIS will be an independent isolated application. Besides isolating shared variable
spaces (like session, application, and server scopes), each application also
Commentaires sur ces manuels