Explore topic-wise InterviewSolutions in Current Affairs.

Cookies are server SPECIFIC simply stored variables stored in files in the BROWSER's file system. It USED to track STATE

Cookies are server specific simply stored variables stored in files in the browser's file system. It used to track state

In structure one can COMBINE VARIABLES of DIFFERENT DATATYPE in to a common data type Whereas arrays are sequentially stored VALUES of the same datatype.

In structure one can combine variables of different datatype in to a common data type Whereas arrays are sequentially stored values of the same datatype.

ColdFusion structures CONSIST of key­value pairs. Structures let you BUILD a collection of related variables that are grouped under a single name. A structure's key must be a string. The values associated with the key can be any valid ColdFusion value or object. It can be a string or INTEGER, or a COMPLEX object such as an array or another structure. Because structures can contain any KIND of data they provide a very powerful and flexible mechanism for representing complex data. check Structure functions here.

ColdFusion structures consist of key­value pairs. Structures let you build a collection of related variables that are grouped under a single name. A structure's key must be a string. The values associated with the key can be any valid ColdFusion value or object. It can be a string or integer, or a complex object such as an array or another structure. Because structures can contain any kind of data they provide a very powerful and flexible mechanism for representing complex data. check Structure functions here.

Session VARIABLES can be used to dump complex data STRUCTURES LIKE ARRAYS and structures.But client variable are used only in case of simple variables.

Session variables can be used to dump complex data structures like arrays and structures.But client variable are used only in case of simple variables.

Flash form is a form LIKE ordinary HTML form, with flash format which RUN on flash player enabled browsers. Using cfform tag CF automatically generates the swf format form's Flash binary from your CFML code. Flash Forms can be USED to create a better forms experience for your users. These features include accordion­style and multiple­tab form panes and automatic element positioning. You can also display cftree, cfgrid, and cfcalendar form elements as Flash

Flash form is a form like ordinary HTML form, with flash format which run on flash player enabled browsers. Using cfform tag CF automatically generates the swf format form's Flash binary from your CFML code. Flash Forms can be used to create a better forms experience for your users. These features include accordion­style and multiple­tab form panes and automatic element positioning. You can also display cftree, cfgrid, and cfcalendar form elements as Flash

Coldfusion introduced easy to use AJAX UI elements. cflayout and cflayoutarea tags used to create tab strips:

<cflayout type="tab">
<cflayoutarea title="Tab 1">
I am normal tab content
</cflayoutarea>
<cflayoutarea title="Tab 2" selected="true">
This tab selected at page load
</cflayoutarea>
<cflayoutarea title="Tab 3" disabled="true">
you can't SEE me, bcz I am in disabled tab
</cflayoutarea>
<cflayoutarea title="Tab 4" closable="true">
U can KILL :) (CLOSE) me
</cflayoutarea>
</cflayout>

Coldfusion introduced easy to use AJAX UI elements. cflayout and cflayoutarea tags used to create tab strips:

<cflayout type="tab">
<cflayoutarea title="Tab 1">
I am normal tab content
</cflayoutarea>
<cflayoutarea title="Tab 2" selected="true">
This tab selected at page load
</cflayoutarea>
<cflayoutarea title="Tab 3" disabled="true">
you can't see me, bcz I am in disabled tab
</cflayoutarea>
<cflayoutarea title="Tab 4" closable="true">
U can kill :) (close) me
</cflayoutarea>
</cflayout>

Database manipulation tags (cfquery, cfstoredproc, cfinsert, cfupdate) have an attribute CALLED DATASOURCE which used to identify/connect to a database. Data sources can be defined in CF ADMINISTRATOR SECTION.

Database manipulation tags (cfquery, cfstoredproc, cfinsert, cfupdate) have an attribute called datasource which used to identify/connect to a database. Data sources can be defined in CF administrator section.

ColdFusion allows DEVELOPERS to REUSE existing queries by running queries against them in memory. This gives you the advantage of being ABLE to avoid the often costly performance hit of going back to the database to manipulate data that the application server has already recently called. A STANDARD <cfquery> statement can be used to call a query variable in memory as though it were simply a table of data in an available data source. Query variables can even be joined, which provides interesting possibilities for joining data from DISPARATE information sources.

ColdFusion allows developers to reuse existing queries by running queries against them in memory. This gives you the advantage of being able to avoid the often costly performance hit of going back to the database to manipulate data that the application server has already recently called. A standard <cfquery> statement can be used to call a query variable in memory as though it were simply a table of data in an available data source. Query variables can even be joined, which provides interesting possibilities for joining data from disparate information sources.

For XML to WORK, both sender and recipient MUST AGREE on an XML LANGUAGE, and all data must be well formed according to that language. WDDX is Macromedia's CONTRIBUTION to the XML community. It is an open­source XML DTD (Document Type Definition) that defines generic data types such as strings, arrays, structures, and recordsets. WDDX is an XML language that defines data not any specific implementation, but raw data itself. This can make data sharing via XML quick and painless (it doesn't require that an XML language be agreed upon).

For XML to work, both sender and recipient must agree on an XML language, and all data must be well formed according to that language. WDDX is Macromedia's contribution to the XML community. It is an open­source XML DTD (Document Type Definition) that defines generic data types such as strings, arrays, structures, and recordsets. WDDX is an XML language that defines data not any specific implementation, but raw data itself. This can make data sharing via XML quick and painless (it doesn't require that an XML language be agreed upon).

It provides a programmatic interface to the COLDFUSION SCHEDULING engine. It can RUN a CFML page at scheduled intervals, with the option to write the page output to a static HTML page. This feature enables you to schedule PAGES that publish data, such as reports, without waiting while a database transaction is performed to POPULATE the page.

It provides a programmatic interface to the ColdFusion scheduling engine. It can run a CFML page at scheduled intervals, with the option to write the page output to a static HTML page. This feature enables you to schedule pages that publish data, such as reports, without waiting while a database transaction is performed to populate the page.

No.Datasource Names For All The Database Tags Within CFTRANSACTION Must Be The Same. The workaround for the problem of CFTRANSACTION with different data source, Use same datasource in CFQUERY but inside the cfquery prefix the table with DESIRED database in the query.

&LT;CFTRANSACTION&GT;
<cfquery datasource=same>
SELECT * FROM TABLENAME
</cfquery>
<cfquery datasource=same>
SELECT * FROM other.dbo.TableName
</cfquery>
</CFTRANSACTION>

No.Datasource Names For All The Database Tags Within CFTRANSACTION Must Be The Same. The workaround for the problem of CFTRANSACTION with different data source, Use same datasource in CFQUERY but inside the cfquery prefix the table with desired database in the query.

<CFTRANSACTION>
<cfquery datasource=same>
SELECT * FROM TableName
</cfquery>
<cfquery datasource=same>
SELECT * FROM other.dbo.TableName
</cfquery>
</CFTRANSACTION>

For enterprise database management systems that SUPPORT transaction processing, INSTRUCTS the database management SYSTEM to treat multiple database operations as a single transaction. It provides database commit and rollback processing. See the documentation for your database management system to determine whether it SUPPORTS SQL transaction processing.
Syntax
isolation = "read_uncommitted|read_committed|repeatable_read"
SAVEPOINT = "savepoint name">

For enterprise database management systems that support transaction processing, instructs the database management system to treat multiple database operations as a single transaction. It provides database commit and rollback processing. See the documentation for your database management system to determine whether it supports SQL transaction processing.
Syntax
isolation = "read_uncommitted|read_committed|repeatable_read"
savepoint = "savepoint name">

Method 1:

<cfinvoke>
<cfinvoke component="user" method="Get"
returnvariable="usr">
<cfinvokeargument NAME="id" value="#id#">
</cfinvoke>

Method 2:

<!­­­ Load CFC as an object ­­­>
<cfobject component="user" name="userObj">
<!­­­ Invoke method ­­­>
<cfinvoke component="#userObj#" method="Get" id="#id#"
returnvariable="usr">
Method 3:

<cfscript>
// Load CFC as an object
userObj=CreateObject("component","user");

// Invoke method

user_id=userObj.Get(id);
</cfscript>

Method 4: URL Invocation : CFCs can also be invoked on the command line directly; EVERY CFC has a URL that POINTS to it. When invoking CFCs via URLs, the method and any arguments are passed as URL parameters, as seen here:

http://localhost/users/user.cfc?method=get&id=1

Method 1:

<cfinvoke>
<cfinvoke component="user" method="Get"
returnvariable="usr">
<cfinvokeargument name="id" value="#id#">
</cfinvoke>

Method 2:

<!­­­ Load CFC as an object ­­­>
<cfobject component="user" name="userObj">
<!­­­ Invoke method ­­­>
<cfinvoke component="#userObj#" method="Get" id="#id#"
returnvariable="usr">
Method 3:

<cfscript>
// Load CFC as an object
userObj=CreateObject("component","user");

// Invoke method

user_id=userObj.Get(id);
</cfscript>

Method 4: URL Invocation : CFCs can also be invoked on the command line directly; every CFC has a URL that points to it. When invoking CFCs via URLs, the method and any arguments are passed as URL parameters, as seen here:

http://localhost/users/user.cfc?method=get&id=1

using cfexecute tag, we can call the external exe files.Below example executes the Windows NT version of the netstat network monitoring program, and places its output in a file.

&LT;cfexecute NAME = "C:WinNTSystem32netstat.exe"
arguments = "­e"
outputFile = "C:Tempoutput.txt"
TIMEOUT = "1">
</cfexecute>

using cfexecute tag, we can call the external exe files.Below example executes the Windows NT version of the netstat network monitoring program, and places its output in a file.

<cfexecute name = "C:WinNTSystem32netstat.exe"
arguments = "­e"
outputFile = "C:Tempoutput.txt"
timeout = "1">
</cfexecute>

• CreateObject() is a functional equivalent of the TAG.
• CreateObject() can be USED to instantiate CFCs just LIKE can, but there is ONE NOTABLE difference: 
• As a function, CreateObject() can be used in a block (whereas cannot).

CFC can be INSTANTIATED as an OBJECT, using the <cfobject> TAG.

CFC can be instantiated as an object, using the <cfobject> tag.

Combination of CFID and CFTOKEN is called as URL token. If user disable the browser COOKIE, It is USED to track a user's browser SESSION. 

Combination of CFID and CFTOKEN is called as url token. If user disable the browser cookie, It is used to track a user's browser session. 

All versions of ColdFusion prior to 6.0 were written USING Microsoft VISUAL C++. CF MX 6.0 move to the Java­ based architecture. Major things introduced in CFMX (MX ­ Matrix, Code name is NEO ­ hero of Matrix).

I POINTED out some of them below:

• Mac,Linux OS support
• Flash Remoting ability to code and debug Flash 
• API was released with an OOP
• Added Verity SEARCHES

All versions of ColdFusion prior to 6.0 were written using Microsoft Visual C++. CF MX 6.0 move to the Java­ based architecture. Major things introduced in CFMX (MX ­ Matrix, Code name is NEO ­ hero of Matrix).

I pointed out some of them below:

For every language has its PROS and CONS. Q5 is answer for this also, But I will POINT out one or 2 advantages of CF over other languages.

• vs PHP : AJAX features, Integration with adobe products, community support, J2EE
• vs JAVA : Easy to learn, Code developmet & maintence cost
• vs .NET : All OS, Most of webserver Support

For every language has its pros and cons. Q5 is answer for this also, But I will point out one or 2 advantages of CF over other languages.

• Simplified INSTALLATION and MIGRATION
• All Operating SYSTEM (OS) Support All Database support
• Faster Development & Easy to Learn
• IMPROVED & support for all Protocols
• access to all the J2EE libraries
• Integration with Other ADOBE Products (Flex, Flash, PDF..)

Cold Fusion is an example of a Common Gateway Interface application. The Common Gateway Interface is a mechanism to allow Web servers, which are designed to serve static documents, to receive dynamic output from programs and serve it as if it were static data.

1. When a browser sends a request for a Cold Fusion template to a Web server, several things MUST HAPPEN. First, the Web server recognizes the information from the browser as a request for CGI output. 
2. If the request was initiated from a form, the server has to write the form field information to some area in storage that is accessible to other programs on the machine. Usually, this is done by using STDOUT data STREAMS. The WinCGI interface, which can be used by WEBSITE and other servers, writes the form data to INI­style files on disk, which are then opened and read by the CGI application.
3. The CGI program requests data from the data source, which is returned in step
4. The CGI program FORMATS the data as HTML output, returning this output to the server in step 
5. The server receives this output, performs any further server­side processing necessary, and then sends it to the browser.

Cold Fusion defaults to using server API modules instead of CGI to communicate between the Web Server and ColdFusion Application Server.

Cold Fusion is an example of a Common Gateway Interface application. The Common Gateway Interface is a mechanism to allow Web servers, which are designed to serve static documents, to receive dynamic output from programs and serve it as if it were static data.

Cold Fusion defaults to using server API modules instead of CGI to communicate between the Web Server and ColdFusion Application Server.

Windows authentication INTRODUCED thorough "cfntauthenticate" tag cfcompile utility introduced which used for Sourceless deployment 

• Administrator API: Change ColdFusion settings programmatically, without logging into the CF Administrator.
• Gateways: SMS, IM (based on Extensible Messaging and Presence PROTOCOL) gateways introduced 
• FLASH forms , Skinnable XML forms introduced 
• New report builder introduced

Windows authentication introduced thorough "cfntauthenticate" tag cfcompile utility introduced which used for Sourceless deployment 

When ColdFusion receives a request for an application page, it searches the page's DIRECTORY for a FILE NAMED Application.cfm. If one exists, the Application.cfm code is LOGICALLY INCLUDED at the beginning of that application page. If your application runs on a UNIX platform, which is casesensitive, you must spell Application.cfm with an initial capital letter.

When ColdFusion receives a request for an application page, it searches the page's directory for a file named Application.cfm. If one exists, the Application.cfm code is logically included at the beginning of that application page. If your application runs on a UNIX platform, which is casesensitive, you must spell Application.cfm with an initial capital letter.

Yes. If the application page directory does not have an Application.cfm page, ColdFusion searches up the directory tree until it FINDS an Application.cfm page. If several DIRECTORIES in the directory tree have an Application.cfm page, ColdFusion uses the first page it finds. If the Application.cfm page is PRESENT in the directory tree (and has the required permissions set), you cannot prevent ColdFusion from INCLUDING it. ColdFusion processes only one Application.cfm page for each request. If a ColdFusion page has a cfinclude TAG pointing to an additional ColdFusion page, ColdFusion does not search for an Application.cfm page when it includes the additional page.

Yes. If the application page directory does not have an Application.cfm page, ColdFusion searches up the directory tree until it finds an Application.cfm page. If several directories in the directory tree have an Application.cfm page, ColdFusion uses the first page it finds. If the Application.cfm page is present in the directory tree (and has the required permissions set), you cannot prevent ColdFusion from including it. ColdFusion processes only one Application.cfm page for each request. If a ColdFusion page has a cfinclude tag pointing to an additional ColdFusion page, ColdFusion does not search for an Application.cfm page when it includes the additional page.

Absolute is from the absolute 0,0 position in the top LEFT CORNER of the browser window. RELATIVE is relative from the positioning of where the DIV is declared WITHIN the html body.

Absolute is from the absolute 0,0 position in the top left corner of the browser window. Relative is relative from the positioning of where the div is declared within the html body.

<STYLE>
table
{
background­color: yellow;
}
td
{
MARGIN: 0 10px 0 0;
}
</style>
<table>
<tr>
<td>HELLO WORLD</td>
</tr>
</table>

<style>
table
{
background­color: yellow;
}
td
{
margin: 0 10px 0 0;
}
</style>
<table>
<tr>
<td>Hello world</td>
</tr>
</table>

.myfontclass
{
font­family: Verdana;
font­weight: bold;
}

.myfontclass
{
font­family: Verdana;
font­weight: bold;
}

Yes. If the application page directory does not have an Application.cfm page, ColdFusion SEARCHES up the directory TREE until it finds an Application.cfm page. If several directories in the directory tree have an Application.cfm page, ColdFusion uses the first page it finds. If the Application.cfm page is present in the directory tree (and has the required permissions set), you cannot prevent ColdFusion from including it.

ColdFusion processes only one Application.cfm page for each request. If a ColdFusion page has a cfinclude TAG pointing to an additional ColdFusion page, ColdFusion does not search for an Application.cfm page when it includes the additional page.

Yes. If the application page directory does not have an Application.cfm page, ColdFusion searches up the directory tree until it finds an Application.cfm page. If several directories in the directory tree have an Application.cfm page, ColdFusion uses the first page it finds. If the Application.cfm page is present in the directory tree (and has the required permissions set), you cannot prevent ColdFusion from including it.

ColdFusion processes only one Application.cfm page for each request. If a ColdFusion page has a cfinclude tag pointing to an additional ColdFusion page, ColdFusion does not search for an Application.cfm page when it includes the additional page.

It defines the scope of a ColdFusion APPLICATION; ENABLES and disables storage of CLIENT variables; specifies the Client variable storage mechanism; enables Session variables; and sets Application variable time­outs.

It defines the scope of a ColdFusion application; enables and disables storage of Client variables; specifies the Client variable storage mechanism; enables Session variables; and sets Application variable time­outs.

We can enable &AMP; disable client management as well as we can configure How & Where client variables need to be STORE

• In the Application.cfc initialization code This.clientmanagement="True" / "false"

This.clientStorage="[Ur_datasource_name]" / "registry" / "cookie" 

• In appliation.cfm using tag attributes clientManagement="yes" / "no"

clientStorage="[Ur_datasource_name]" / "registry" / "cookie"

[Ur_datasource_name] ­ Stored in ODBC or native data source. You must CREATE storage REPOSITORY in the Administrator. registry ­ Stored in the system registry. cookie ­ Stored on client computer in a cookie. Scalable. If client disables cookies in the browser, client variables do not work.

We can enable & disable client management as well as we can configure How & Where client variables need to be store

This.clientStorage="[Ur_datasource_name]" / "registry" / "cookie" 

clientStorage="[Ur_datasource_name]" / "registry" / "cookie"

[Ur_datasource_name] ­ Stored in ODBC or native data source. You must create storage repository in the Administrator. registry ­ Stored in the system registry. cookie ­ Stored on client computer in a cookie. Scalable. If client disables cookies in the browser, client variables do not work.

ApplicationTimeout : The TIME span an application will exist before it times out (if the application is not accessed in any WAY). This defaults to the VALUE set in the ColdFusion administrator.
SessionTimeout : The time span a SESSION will exist before it times out (if the application is not access in any way by that session's user). This defaults to the value set in the ColdFusion administrator.

ApplicationTimeout : The time span an application will exist before it times out (if the application is not accessed in any way). This defaults to the value set in the ColdFusion administrator.
SessionTimeout : The time span a session will exist before it times out (if the application is not access in any way by that session's user). This defaults to the value set in the ColdFusion administrator.

To Flush CACHED QUERIES <cfobjectcache ACTION="CLEAR">
To Flush cached pages <cfcache action="flush">

To Flush cached queries <cfobjectcache action="clear">
To Flush cached pages <cfcache action="flush">

Stored procedures abstract database logic from server side code. They ALSO offer PERFORMANCE benefits in pushing APPLICATION logic to the database side. The disadvantage is that if they are POORLY written then they can hinder database performance and make development a LITTLE more obfuscated.

Stored procedures abstract database logic from server side code. They also offer performance benefits in pushing application logic to the database side. The disadvantage is that if they are poorly written then they can hinder database performance and make development a little more obfuscated.

SET QUOTED_IDENTIFIER ON 
GO 
SET ANSI_NULLS ON
GO
CREATE PROCEDURE [dbo].getDirector (
@movie_id INT
)
SELECT NAME FROM directors WHERE movie_id = @movie_id
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON 
GO 
SET ANSI_NULLS ON
GO
CREATE procedure [dbo].getDirector (
@movie_id INT
)
SELECT name FROM directors WHERE movie_id = @movie_id
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO

movie_id.

movie_id.

SELECT MOVIE.title, DIRECTOR.name FROM movie LEFT JOIN director ON movie.id = director.movie_id .

SELECT movie.title, director.name FROM movie LEFT JOIN director ON movie.id = director.movie_id .

&LT;cfmodule TEMPLATE=”testmod.cfm” 
param1=”YES”
param2=5&GT;

<cfmodule template=”testmod.cfm” 
param1=”yes”
param2=5>

ColdFusion is implemented on the J2EE. J2EE is a standard, it is not a programming language. J2EE is an IMPLEMENTATION of the Java programming language, but includes a number of Application Programming Interfaces (APIs) for connecting to databases, queuing messages, connecting to registries and naming and directory services. All of these APIs are USED by coldfusion for many of its BASE services and other RUNTIME services. 

ColdFusion consists of following components:

• cf script
• CFML
• ColdFusion Administrator
• Verity SEARCH Server

ColdFusion is implemented on the J2EE. J2EE is a standard, it is not a programming language. J2EE is an implementation of the Java programming language, but includes a number of Application Programming Interfaces (APIs) for connecting to databases, queuing messages, connecting to registries and naming and directory services. All of these APIs are used by coldfusion for many of its base services and other runtime services. 

ColdFusion consists of following components:

A computer that delivers (serves up) Web pages. Every Web SERVER has an IP address and possibly a domain NAME. For example, if you enter the URL http://www.domainname.com/index.html in your browser, this sends a request to the server whose domain name is domainname.com. The server then fetches the page named index.html and sends it to your browser. Any computer can be TURNED into a Web server by installing server software and connecting the machine to the Internet. There are many Web server software APPLICATIONS, including public domain software from NCSA and Apache, and commercial packages from Microsoft, Netscape and others.

A computer that delivers (serves up) Web pages. Every Web server has an IP address and possibly a domain name. For example, if you enter the URL http://www.domainname.com/index.html in your browser, this sends a request to the server whose domain name is domainname.com. The server then fetches the page named index.html and sends it to your browser. Any computer can be turned into a Web server by installing server software and connecting the machine to the Internet. There are many Web server software applications, including public domain software from NCSA and Apache, and commercial packages from Microsoft, Netscape and others.

A server that exposes business LOGIC to client applications through various protocols including HTTP, HTTPS, IIOS/SSL.

Eg: Sun Java Application server, weblogic server It TAKES CARE of important ISSUES like Transaction Management, Security, Database Connection Pooling, Clustering, Scalability,session management,load balancing,thread management and Messaging etc. A web server cannot provide these.

A server that exposes business logic to client applications through various protocols including HTTP, HTTPS, IIOS/SSL.

Eg: Sun Java Application server, weblogic server It takes care of important issues like Transaction Management, Security, Database Connection Pooling, Clustering, Scalability,session management,load balancing,thread management and Messaging etc. A web server cannot provide these.

While debugging is mainly used to debug the CODE and to see run time values. Especially for trouble shooting. How ever, once the PROGRAMS are in production server, we can not debug, but to avoide users seeing all the error messages when a program unexpectedly failed and throwing errors, we can use error handling methods. TRY and CATCH is the best AMONG them to handle any database RELATED errors.

<cftry>
Here is your actual code…of coldfusion….
</cfcatch>

Write your message to the user in case of any error.

</cfcatch>
</cftry>

While debugging is mainly used to debug the code and to see run time values. Especially for trouble shooting. How ever, once the programs are in production server, we can not debug, but to avoide users seeing all the error messages when a program unexpectedly failed and throwing errors, we can use error handling methods. TRY and CATCH is the best among them to handle any database related errors.

<cftry>
Here is your actual code…of coldfusion….
</cfcatch>

Write your message to the user in case of any error.

</cfcatch>
</cftry>

(COLDFUSION FTP ­ <cfftp&GT;) : By using coldfusion <cfftp> tag, we can SEND data from LOCAL computer to the SERVER and also retrieve the data from server to the local computer. By using Get file, we can retrieve data from server:

<cfftp
action="getFile"
server="127.0.0.1"
username="user1"
password="pass1"
remotefile="/abcd.jpeg"
localfile="C:examples/efgh.jpg"
failIfExists="no">
By usingPut file, we can send data to the server:

<cfftp action="putFile"
server="127.0.0.1"
username="user1"
password="pass1"
localfile="C:examples/efgh.jpg"
remotefile="/abcd.jpeg"
failIfExists="no">

(coldfusion FTP ­ <cfftp>) : By using coldfusion <cfftp> tag, we can send data from local computer to the server and also retrieve the data from server to the local computer. By using Get file, we can retrieve data from server:

<cfftp
action="getFile"
server="127.0.0.1"
username="user1"
password="pass1"
remotefile="/abcd.jpeg"
localfile="C:examples/efgh.jpg"
failIfExists="no">
By usingPut file, we can send data to the server:

<cfftp action="putFile"
server="127.0.0.1"
username="user1"
password="pass1"
localfile="C:examples/efgh.jpg"
remotefile="/abcd.jpeg"
failIfExists="no">

Coldfusion provides us many debugging options in order to trouble shoot a coldfusion program.

The important are:
CFDUMP, eg: <cfdump VAR="#abcd#"&GT;
CFABORT, eg: <cfabort>

On the debugging settings in coldfusion ADMINISTRATOR. (you will see the lengthy debugging information at the bottom of the coldfusion RESULT).

Coldfusion provides us many debugging options in order to trouble shoot a coldfusion program.

The important are:
CFDUMP, eg: <cfdump var="#abcd#">
CFABORT, eg: <cfabort>

On the debugging settings in coldfusion administrator. (you will see the lengthy debugging information at the bottom of the coldfusion result).

COLDFUSION has a beautiful feature called Query of Queries which is MAINLY used for improving PERFORMANCE of the application. Query of Queries is the RESULT of an existing DATABASE query result.This will be done by using coldfusion “cfquery” tag and need to
specify dbtype = ‘query’.

Eg:
select *
from NameOfAnotherQuery
where ColumnName = 'SomeValue'

Coldfusion has a beautiful feature called Query of Queries which is mainly used for improving performance of the application. Query of Queries is the result of an existing database query result.This will be done by using coldfusion “cfquery” tag and need to
specify dbtype = ‘query’.

Eg:
select *
from NameOfAnotherQuery
where ColumnName = 'SomeValue'

By using cffile tag, we can upload a FILE to the server.

A TYPICAL cffile syntax is:

<cffile action="upload" 
fileField="fileUpload"
 DESTINATION="C:DOCS">

By using cffile tag, we can upload a file to the server.

A typical cffile syntax is:

<cffile action="upload" 
fileField="fileUpload"
 destination="C:docs">

ClientManagement can be enabled and disabled as and when we need depending upon the requirement. 

• In the Application.cfc initialization code This.clientmanagement="True" / "false"

This.clientStorage="[Ur_datasource_name]" / "registry" / "cookie"

• In appliation.cfm using tag attributes clientManagement="YES" / "no"

clientStorage="[Ur_datasource_name]" / "registry" / "cookie"

[Ur_datasource_name] ­ STORED in ODBC or native data source.You must create storage REPOSITORY in the Administrator. registry ­ Stored in the SYSTEM registry.cookie ­ Stored on client computer in a cookie. Scalable. If client disables cookies in the browser, client variables do not WORK.

ClientManagement can be enabled and disabled as and when we need depending upon the requirement. 

This.clientStorage="[Ur_datasource_name]" / "registry" / "cookie"

clientStorage="[Ur_datasource_name]" / "registry" / "cookie"

[Ur_datasource_name] ­ Stored in ODBC or native data source.You must create storage repository in the Administrator. registry ­ Stored in the system registry.cookie ­ Stored on client computer in a cookie. Scalable. If client disables cookies in the browser, client variables do not work.

NAME, clientStorage, LoginStorage, CLIENTMANAGEMENT, ApplicationTimeout, SetclientCcookies, SessionTimeout ETC.. 

Name, clientStorage, LoginStorage, ClientManagement, ApplicationTimeout, SetclientCcookies, SessionTimeout etc.. 

Application.cfm page will be used to define application level variables, for example instead of DECLARING dsn VARIABLE in every query you use, you can define the variable in application.cfm page once and can use that variable in every ColdFusion page you use queries to retrieve data from DATABASE. We can definitely use more than ONE application.cfm pages, however, only the first application.cfm page that the ColdFusion server finds, will be used. Application.cfm page is not mandatory.

Application.cfm page will be used to define application level variables, for example instead of declaring dsn variable in every query you use, you can define the variable in application.cfm page once and can use that variable in every ColdFusion page you use queries to retrieve data from database. We can definitely use more than one application.cfm pages, however, only the first application.cfm page that the ColdFusion server finds, will be used. Application.cfm page is not mandatory.

ColdFusion 9.0 has many benefits over older versions and to name few they are:
Coldfusion can be used as a service with out writing lines of code, we can get results by using: CFChart, Cfdocument, CFImage, CFmail, CFPDF and cfpop etc. And also these services can be sandboxed in ORDER to GIVE more security. ADOBE AIR database synchronization. New AJAX controls are added. Server manager is a new feature by which from one access point we can MANAGE several admin TASKS of various servers. Also ColdFusion 9 allows you to create coldfusion component as a portlet. 

ColdFusion 9.0 has many benefits over older versions and to name few they are:
Coldfusion can be used as a service with out writing lines of code, we can get results by using: CFChart, Cfdocument, CFImage, CFmail, CFPDF and cfpop etc. And also these services can be sandboxed in order to give more security. Adobe AIR database synchronization. New AJAX controls are added. Server manager is a new feature by which from one access point we can manage several admin tasks of various servers. Also ColdFusion 9 allows you to create coldfusion component as a portlet. 

New era STARTED for ColdFusion from MX versions.. such as Mac, LINUX support, FLASH remoting new Variety search functionalityand code and debug of flash COMPONENTS.

New era started for ColdFusion from MX versions.. such as Mac, Linux support, Flash remoting new Variety search functionalityand code and debug of flash components.