<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2>Hi Chris,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2>I'll give this a shot, though my technical understanding
may not be perfect.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2>The FCGI handler is pointing to a FastCGI server
process (<A href="http://www.fastcgi.com/">http://www.fastcgi.com/</A>).
This is similar to ISAPI modules; it keeps the executable in memory, allows
shared connections, etc, etc. It gives most of the benefits of
server-specific modules (isapi, apache modules) without requiring the developers
to develop for each of these architectures.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2>Similar to ISAPI modules, using FastCGI does not require
that the server spawn a new PHP interpreter for each page request. This
gives considerably better performance, though it does mean that the developers
can't be sloppy about memory leaks.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2>One unintended benefit of using FastCGI is that you can
have multiple PHP installs, each with their own INI file, while retaining the
benefits of a persistent process. With the PHP ISAPI module on IIS, you
can't do this.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2>Early releases of MapGuide had problems with the way that
the handlers were set up, but I haven't personally seen any issues with
1.0.2.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=329435218-15112006><FONT face=Arial
color=#0000ff size=2>Jason</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Chris Gountanis<BR><B>Subject:</B>
[mapguide-users] isapi_fcgi.dll <BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial size=2><FONT size=2>
<P>With that being said is there a better way to setup the IIS/PHP config in
IIS. I was told be a few people that they had to change the PHP and FCGI
handlers manually after the fact. Why are PHP pages handled with the
isapi_fcgi.dll file and not the php-cgi.exe file? What is the big diff from
using mapagent.fcgi or using MapAgent.exe directly. What is the fcgi file
actually redirecting to?</P></FONT></FONT></DIV>
<DIV>--<BR>Chris<BR></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>