Changes between Version 2 and Version 3 of MapGuideRfc22

Timestamp:

Jun 29, 2007, 10:28:09 AM (17 years ago)

Author:

ronnielouie

Comment:

--

MapGuideRfc22

@@ -8 +8 @@
  
 ||RFC Template Version||(1.0)|| 
-||Submission Date||(Date/Time submitted)||
-||Last Modified||(your name here) [[Timestamp]]||
-||Author||(your name here)||
-||RFC Status||(draft, proposed, frozen for vote, adopted, retracted, or rejected)||
-||Implementation Status||(pending, under development, completed)||
-||Proposed Milestone||(e.g. 1.1, 1.3)||
+||Submission Date||June 29, 2007||
+||Last Modified||Ronnie Louie [[Timestamp]]||
+||Author||Ronnie Louie||
+||RFC Status||draft||
+||Implementation Status||pending||
+||Proposed Milestone||1.3||
 ||Assigned PSC guide(s)||(when determined)||
 ||'''Voting History'''||(vote date)||
@@ -33 +33 @@
 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.
+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 for addressing stability, performance and other issues.
 
 == Proposed Solution ==
 
-This is a more detailed description of the actual changes desired.  The contents of this section will vary based on the target of the RFC, be it a technical change, website change, or process change.  For example, for a technical change, items such as files, XML schema changes, and API chances would be identified.  For a process change, the new process would be laid out in detail.  For a website change, the files affected would be listed.
+The existing FastCGI agent will be removed and replaced with a new ISAPI extension and Apache module.  Much of the request handling that is currently performed by the FastCGI agent will be implemented instead in the new ISAPI extension or Apache module.  These modules will interface directly with the web server and will parse the http request parameters for creating a server request to be executed by the MapGuide Server.  The response will be returned to the web server which sends the response back to the client.  Complete round trip processing of the request is expected to be at least equal to or greater than the performance when using FastCGI.
+
+
+
 
 == Implications ==
 
-This section allows discussion of the repercussions of the change, such as whether there will be any breakage in backwards compatibility, if documentation will need to be updated, etc.
+FastCGI will no longer be used, however existing applications that use .fcgi in the url (i.e. http://localhost/mapguide/mapagent/mapagent.fcgi?OPERATION=ENUMERATERESOURCES&VERSION=1.0.0&LOCALE=en&RESOURCEID=Library://&TYPE=&DEPTH=-1)  can continue to work if the web server is configured to map the .fcgi extension to the new ISAPI module.  This re-mapping can be done automatically by the installer.
+
+Installers will need to be modified to install the ISAPI extension for IIS, or the Apache module for Apache web server.
+
 
 == Test Plan ==
 
-How the proposed change will be tested, if applicable.  New unit tests should be detailed here???
+Tests will need to be done to evaluate the performance and stability of the ISAPI and Apache modules against FastCGI.
 
 == Funding/Resources ==
 
-This section will confirm that the proposed feature has enough support to proceed.  This would typically mean that the entity making the changes would put forward the RFC, but a non-developer could act as an RFC author if they are sure they have the funding to cover the change.
+Autodesk