Share this Page URL
Help

Day 1. Introducing ColdFusion > How ColdFusion Works Within the Client/Server R... - Pg. 11

Introducing ColdFusion 11 When the server receives a request from a client, it performs whatever function the client has re- quested. Most often, the client has requested an HTML page or an image file, so the server's task is simple--send the requested file back to the client. Pull out your highlighter now, because here comes the key concept: Sometimes the client's request, though still a URL, asks that the server perform an action, and then return the results of that action to the user's browser. This is the basis of the CGI scripts mentioned previously, and it is the key element that makes the wonder of dy- namically generated pages possible. When a client requests a ColdFusion template or the name of a CGI script, the server performs an action--depending on the request, it might search a database, run a computation on figures, or run a short program. It then returns the output, or results of the action, to the client in the form of an HTML document. The client doesn't care what goes on behind the scenes; it's only concerned with the HTML output. How ColdFusion Works Within the Client/Server Relationship In the client/server relationship, ColdFusion resides on the server computer, running in conjunction with Web server software. It waits for a client to send a request URL that has the .CFM extension designating a ColdFusion template file, such as http://www.blahblah.com/stuff.cfm and then goes to work. It momentarily seizes control on the Web server, does whatever is requested of it in the template file, and then gives the results back to the Web server to hand over to the magic fairies for delivery to the client. Tag Processing