> If indeed Inetinfo is the leaking process, then chances are it's
> Allaire's CFML.dll that's the culprit. That runs inprocess w/ IIS
> and calls out to the CFServer.exe process. I've never quite
> understood why Allaire felt a need to program their server out of
> process, but....
I have some ideas about why the CF server runs as a separate process.
First, it's always run as a separate process, since before web servers had
APIs. Prior to CF 2, the way that CF worked was that you'd have a URL which
looked something like this:
http://www.yoursite.com/cgi-bin/dbml.exe?template=/somefile.cfm
CF would install a CGI stub program, dbml.exe, which you'd put into a
CGI-enabled directory. Every time that your web server got a request that
looked like the one above, it would start another copy of dbml.exe, which
would simply push the data stream to the CF service.
Another reason that it might work better as a separate process is that it
might be able to do things that it might not be able to do as easily running
as a part of the web server's process. For example, the use of shared
Application and Server memory scopes seems like it'd be easier to make
happen this way.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
