MACROMEDIA COLFUSION MX 7-CFML Podręcznik Użytkownika Pobierz pdf (Strona 23)

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

• Leveraging .NET Tracing/Debugging Output

o It is possible to configure web applications in the .NET framework so that you

can enable tracing/debugging output to be created either on a given page or in an

available trace monitoring page (trace.axd) that can track output from any page

request from any user. For more information, see:

Where the mechanisms to enable these features are not documented here, and to learn about

many more, see the Microsoft documentation or various books, articles, blogs, and web sites.

Additionally, see the resources listed in section

http://www.dotnetjunkies.com/quickstart/aspplus/doc/tracelogapp.aspx

4.2 CFML-based Database Processing is ADO.NET under the Covers

Another benefit of the .NET Framework which generally requires no changes in CFML code is

the fact that when performing CFQUERY and other database tags, the .NET edition of BlueDra-

gon leverages ADO.NET under the covers. (The Java editions of BlueDragon and CFMX leve-

rage JDBC for database processing, instead.)

Some of the advantages of ADO.NET are described in this section. Note that your CFML tags,

and even the admin console datasource configuration process, remain substantially unchanged.

Under the covers, the query objects created are ADO.NET, and as such they benefit from the im-

proved performance and reliability of having database processing mechanisms that are created by

Microsoft rather than a third party (as with the CFMX database drivers from DataDirect).

Following are some advantages from BlueDragon leveraging ADO.NET.

4.2.1 CFQUERY Results Are ADO.NET DataTables, and Vice-versa

BlueDragon automatically causes CFQUERY results to be treated in ASP.NET as .NET data-

tables, and vice-versa. Various features regarding sharing of data between CFML and ASP.NET,

as discussed in section 3.2.2, demonstrate leveraging this feature.

4.2.2 ADO.NET Connection Pooling

One advantage of the underlying ADO.NET implementation is its support for enhanced connec-

tion pooling. By default, datasources defined in the BlueDragon Admin console use a connection

pooling mechanism that is built into BlueDragon. You can cause BlueDragon to give up control

of connection pooling for a given datasource, so that ADO.NET connection pooling takes its

place.

In the BlueDragon Admin console, where a datasource is defined, there is an available Maximum

Connections

field, which defaults to 24. If this value is set to 0, BlueDragon will not perform

connection pooling. Further, you can specify details about how to configure ADO.NET connec-

tion pooling by passing appropriate values into the Connection String field on the same

page.

For more information on setting these values in the Admin console, see the online help link on

the page where a datasource is defined.

1 2 ... 18 19 20 21 22 23 24 25 26 27 28 ... 55 56

Brak uwag

MACROMEDIA COLFUSION MX 7-CFML Podręcznik Użytkownika Strona 23