MACROMEDIA COLFUSION MX 7-CFML Guía de usuario descargar pdf (Pagina 43)

BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 38

7.1.3 Implications on Sessions of Restarting .NET Web Applications

One of the most important implications of restarting web applications is that, assuming session

variables are stored in memory (which is the default in .NET) and you are using .NET sessions

for your CFML, when the web application restarts, all session variables will be lost.

As discussed in Section 4, it’s possible to declare that a .NET web application should use an

alternative form of persistence, including a database or state server. One benefit of those options

is that when a .NET web application is restarted, the session variables are recovered, thereby mi-

nimizing the impact to end users of such application restarts.

If your CFML applications use session variables and your application is suffering frequent res-

tarts for any of the manual or automated reasons explained previously in this section, you should

consider using session variable persistence.

7.1.4 First Request Delay on Restart of .NET Web Applications

Another facet of the impact of restarting a .NET web application (whether manually or automati-

cally) is a slight delay upon the first request for a page in a .NET web app. The delay occurs only

for the first user making a request for any dynamic page (.aspx or .cfm files, for instance, not

.htm or .gif files) after the restart. The delay may be up to a few seconds. This is not a BlueDra-

gon issue, but a generic .NET one.

One solution, if your web applications are stopped on a recurring basis, would be to set up a

scheduled task (using the Windows scheduler) that makes a request for any dynamic page. Per-

haps it could be set to run first thing in the morning every day (if the server is restarted nightly,

perhaps due to changes as described in section 7.1.2).

Another option may be to take advantage of .NET’s ability (via the special global.asax file)

to set up an application end event, so that whenever the web application is stopped, a request is

made to start it again. Just be aware that you may have a reason some times for the web applica-

tion to stop and not be immediately restarted.

7.2 Manually Configuring CFML Extension Mappings

You may want or have to manually configure the CMFL extension mappings in IIS, as discussed

in the following sections.

7.2.1 “Manual Configuration” Installation Option

If you choose the Manual Configuration option in the BlueDragon.NET installer, you must

then manually implement the extension mappings for CFML-based file extensions, including

CFM, CFC, CFCHART, and CFML. You may also desire to manually configure these extension

mappings even if you’ve used one of the other installation options (such as when resolving the

problem discussed in Section 8.1.2.1).

In BlueDragon.NET, the mapping for all CFML extensions should point to the same executable

as ASP.NET pages (like ASPX and ASMX), the aspnet_isapi.dll. In a .NET 2.0 installation,

this will generally be:

1 2 ... 38 39 40 41 42 43 44 45 46 47 48 ... 55 56

Sin comentarios

MACROMEDIA COLFUSION MX 7-CFML Guía de usuario Pagina 43