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

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

7.2.3 Hiding CFM Extensions

http://www.west-wind.com/Tools/WebSiteConfiguration.asp

As you contemplate the steps in this section, be aware that you cannot install BlueDragon more

than once on a given machine. If you already have implemented any of the other installation op-

tions, you cannot run the installer again to use the fourth option to create a single virtual direc-

tory deployment. Instead, you must either uninstall BlueDragon or run the installer on a machine

(or virtual machine) that does not yet have BlueDragon installed.

You may also choose to manually configure a different file extension to process CFML pages.

You could, for instance, declare that .xyz files should be processed by BlueDragon as CFML.

You would need to change both IIS extension mappings as described in section 7.2.1 and the

HttpHandler settings described in 6.3.

The steps to do this (including for BlueDragon editions other than the .NET version) are dis-

cussed in a BlueDragon technote, “"Hiding" CFML behind an extension other than .cfm or

.cfml”:

7.3 Sourceless Deployment

http://www.newatlanta.com/products/bluedragon/self_help/tech_notes/hiding_

cfml.cfm

BlueDragon supports sourceless deployment (deploying your CFML applications without ex-

posing your source code) through an option we call precompiling and optionally encrypting your

CFML templates. This protects your code from being read. (The files are not converted into

.NET classes or DLLs but instead remain CFM files, which when opened are unreadable, and no

mechanism exists to revert them to source.) This feature is discussed in the BlueDragon 7.1 User

Guide

While the BlueDragon admin console provides an option for precompiling templates, there is

also an available command line utility. In BlueDragon.NET, the precompile.exe utility is lo-

cated in the

precompiler directory where BlueDragon is installed. There are important addi-

tional details offered in a

readme.txt file located there.

7.3.1 Setting an Expiration Date on Your Templates, Such as for Trial Code

An extension of the precompiled code feature (from the last section), BlueDragon permits you to

set an expiration date for your code, whether for a single template, directory, or an entire CFML

application. With this feature, such code will stop working after a given date (reporting to the

user an appropriate message).

Note that BlueDragon will continue to run, as this is an expiration date for just your code, so you

can have some part of your application continue to run while some other portion stops on that

date. If and when the user obtains the permission from you to use the code beyond that date, you

simply provide new copies of the CFML code to be dropped into the appropriate directory of

your application.

1 2 ... 41 42 43 44 45 46 47 48 49 50 51 ... 55 56

Sin comentarios

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