Thanks Dave, That is about the level that I am trying to understand. I want to take this step by step.
You said: 2. Web server module/filter/whatever identifies the URL pattern of the request as a CF request, and forwards the request to the CF server itself, which is listening on its own port. The web server module is the connector that is described in the documentation, correct? This connector is really the JRun connector, correct? The web server will ask each module (php, jsp, cfm, asp, static) to handle the request. If the request is a CF template, the other modules will ignore the request and pass the request to the next module until the JRun connector says, "hey this request goes to a coldfusion server." The connector passes the request to a coldfusion server and the coldfusion server accepts it. How am I doing so far? Thanks, Troy On 7/28/06, Dave Watts <[EMAIL PROTECTED]> wrote: > > I am looking for information on the details of how ColdFusion > > MX 7 receives a request, compiles the cfml into java and then > > execute the code. > > > > I have looked all over the web and I have only found bits and pieces. > > I suspect that, unless you remove Tim Buntel's brain, you will only find > bits and pieces of how this works. So, you might try to describe what > exactly you want to know, other than "everything". > > That said, here's basically what happens. > > 1. Web server receives request. > 2. Web server module/filter/whatever identifies the URL pattern of the > request as a CF request, and forwards the request to the CF server itself, > which is listening on its own port. > 3. The CF server identifies the file matching the URL pattern. > 4. The CF server checks its memory cache for an existing Java class > corresponding to the file. > 5. If the cache doesn't contain the class, the CF server checks for an > existing Java class within the /WEB-INF/cfclasses directory if the "Save > class files" option is enabled in the CF Administrator. > 6. If it's not there either, the CF server reads the file from disk and > compiles it directly to bytecode (no .java file is created). I believe that > Jikes is used for this, although I'm not sure. The bytecode is then stored > in memory and optionally on disk. > 7. The compiled Java class is executed. The output generated by this is > stored in a buffer, then returned to the web server after completion. > 8. The web server returns it to the browser. > > If you have any questions about specific portions of the process, let me > know and I'll answer them if I can. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > > Fig Leaf Software provides the highest caliber vendor-authorized > instruction at our training centers in Washington DC, Atlanta, > Chicago, Baltimore, Northern Virginia, or on-site at your location. > Visit http://training.figleaf.com/ for more information! > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:248100 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
