Changes between Version 3 and Version 4 of MapGuideRfc80

Timestamp:

Aug 6, 2009, 5:32:48 PM (15 years ago)

Author:

leaf

Comment:

--

MapGuideRfc80

@@ -28 +28 @@
 == Motivation ==
 
-Currently FDO interface supports parameter binding when executing an FdoISQLCommand. Method GetParameterValues() returns a parameters value collection and users can set value for each named parameter. However, MapGuide Feature Service doesn’t provide this capability. This RFC will add two methods into Feature Service API to eliminate this limitation.  
+Currently FDO interface supports parameter binding when executing an FdoISQLCommand. Method !GetParameterValues() returns a parameters value collection and users can set value for each named parameter. However, MapGuide Feature Service doesn’t provide this capability. This RFC will add two methods into Feature Service API to eliminate this limitation.  
 
 == Proposed Solution ==
@@ -34 +34 @@
 ==== Parameter Direction ====
 
-The !MgParameterDirection defines integer constants used to signify the direction in which command will utilize the parameter upon execution. Parameter direction values are typically Input, Output, InputOutput and Return, with the default value is typically Input.
+The !MgParameterDirection defines integer constants used to signify the direction in which command will utilize the parameter upon execution. Parameter direction values are typically Input, Output, !InputOutput and Return, with the default value is typically Input.
 
 {{{
-///////////////////////////////////////////////
 /// \brief
 /// The MgParameterDirection defines integer constants used to signify the 
@@ -654 +653 @@
 == Implications ==
 
-This RFC depends on FDO RFC 33 (http://trac.osgeo.org/fdo/wiki/FDORfc33), which improves parameter binding to support specifying parameter direction. If FDO RFC 33 can’t get approved, we will not remove class MgParameterDirection and method MgParameter::SetDirection(...) and MgParameter::GetDirection() in this RFC.
+This RFC depends on FDO RFC 33 (http://trac.osgeo.org/fdo/wiki/FDORfc33), which improves parameter binding to support specifying parameter direction. If FDO RFC 33 can’t get approved, we will not remove class !MgParameterDirection and method MgParameter::SetDirection(...) and MgParameter::GetDirection() in this RFC.
 
 == Test Plan ==