> I have noticed in your various posts that you refer to CF > as well as things like mod_perl as a CGI environment. Why? > CGI stands for common gateway interface. It is an API to > allow a web server to execute an application to handle > certain requests. While ColdFusion can operate in CGI mode, > almost nobody does that. ColdFusion requests are generally > handed off to ColdFusion via ISAPI (IIS), NSAPI (Netscape/ > iPlanet), or module (Apache). Further, as the name states, > mod_perl is not a CGI based implementation, it is in fact > handling requests through the Apache module interface.
For the sake of convenience, mostly. The only significant difference between a "true" CGI application and an application that uses a specific web server API is the method in which the application is invoked - rather than starting an executable, passing data to that executable, and waiting for the executable to shut down, the same data, essentially, is passed to an in-process object. In short, I find "CGI" to be a good, understandable, generic way to refer to web-based applications - when I do so, people generally seem to understand what I'm referring to. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
