Changes between Version 1 and Version 2 of MapGuideRfc22

Timestamp:

Jun 29, 2007, 8:57:06 AM (17 years ago)

Author:

ronnielouie

Comment:

--

MapGuideRfc22

@@ -23 +23 @@
 == Overview ==
 
-This section brefly describes the problem set, and the proposed solution in general terms.  It should be deliberately short, a couple of sentences or so.
+This RFC proposes to replace the FastCGI agent on the web-tier with an ISAPI extension and Apache module for IIS and Apache webservers respectively.
 
 == Motivation ==
 
-This is the most important part of the RFC.  It describes the problem domain in detail.  Focusing on this will allow reviewers to fully understand why the proposed change is being made, and potentially suggest different/better ways of accomplishing the desired results.  The more time we spend on understanding the problem, the better our solution will be.
+FastCGI is a protocol for a high performance alternative to CGI for interfacing internet applications with a web server.  Current use of FastCGI has revealed some stability and performance issues relating to this technology (http://trac.osgeo.org/mapguide/ticket/129).  
+
+The current FastCGI implementation for Microsoft Internet Information Server (IIS) was released in 2002 and has not been maintained.  IIS 7 is supposed to feature built-in FastCGI support, however it currently is in beta and should not be considered for use in a production environment.
+
+The Apache module for FastCGI also has not been maintained as the current implementation was released in 2003.  More recently, a binary compatible alternative FastCGI module has been developed by another third party developer to address process management issues, but it's stability and performance is rather unknown.
+
+By replacing the FastCGI agent with an ISAPI extension or an Apache module, the web-tier will be using more proven and stable technologies, as well as reducing the dependency on third party development to address stability and performance issues.
 
 == Proposed Solution ==