[mapserver-commits] r7546 - trunk/mapserver/rfc

svn at osgeo.org svn at osgeo.org
Wed Apr 30 10:27:38 EDT 2008


Author: dmorissette
Date: 2008-04-30 10:27:38 -0400 (Wed, 30 Apr 2008)
New Revision: 7546

Modified:
   trunk/mapserver/rfc/ms-rfc-42.txt
Log:
Updated status to completed

Modified: trunk/mapserver/rfc/ms-rfc-42.txt
===================================================================
--- trunk/mapserver/rfc/ms-rfc-42.txt	2008-04-30 14:19:30 UTC (rev 7545)
+++ trunk/mapserver/rfc/ms-rfc-42.txt	2008-04-30 14:27:38 UTC (rev 7546)
@@ -5,9 +5,10 @@
 :Date: 2008/03/26
 :Author: Julien-Samuel Lacroix
 :Contact: jlacroix at mapgears.com 
-:Status: Development
+:Last Edited: 2008/04/01
+:Status: Adopted 2008/04/01 - Implementation completed
+:version: MapServer 5.2
 
-
 ==============================================================================
 Overview
 ==============================================================================
@@ -57,6 +58,7 @@
 ==============================================================================
 Implementation Issues
 ==============================================================================
+
 It was pointed out during the RFC review period that passing and storing the cookie data using an "http_cookie_data" metadata is a poor use of MapServer's metadata mechanism.
 
 Since MapServer currently lacks a mechanism to associate application state information to a mapObj, there is currently no better mechanism in place to store the cookie data received from the client and pass it to the rendering code that calls the remote WMS. Due to lack of a better solution, for the time being we will use the "http_cookie_data" metadata as proposed in this RFC, with the knowledge that this is a poor use of metadata and that we as soon as a better mechanism is in place to store and pass application state in a mapObj then this metadata will be deprecated and replaced by this new mechanism. Developers of MapScript applications setting this "http_cookie_data" metadata should be aware of this and be prepared to change their code in future revisions of MapServer. 



More information about the mapserver-commits mailing list