Changes between Version 4 and Version 5 of MapGuideRfc105

Timestamp:

Jul 21, 2010, 2:41:08 PM (14 years ago)

Author:

brucedechant

Comment:

--

MapGuideRfc105

@@ -24 +24 @@
 == Overview ==
 
-This RFC proposes to update the feature service !GetCapabilites() API by adding an additional connection string parameter.
+This RFC proposes to add a NEW !GetCapabilites() API to the feature service which contains an additional connection string parameter. This will primarily allow for acquiring the "runtime" capabilities of WFS/WMS providers.
 
 == Motivation ==
@@ -59 +59 @@
 == Proposed Solution ==
 
- * The new connection string parameter will be added to the !GetCapabilities() API. This NEW parameter will cause the API to behave exactly as before if it is an empty string.
+ * Create a NEW !GetCapabilites() API that takes an additional connection string parameter. This NEW parameter will cause the API to behave exactly as before if it is an empty string.
 
 Existing API:
@@ -66 +66 @@
 }}} 
 
-Proposed API:
+Proposed NEW API:
 {{{
     MgByteReader* GetCapabilities(CREFSTRING providerName, CREFSTRING connectionString);
@@ -73 +73 @@
 == Implications ==
 
-This change will break existing API compatibility if we replace the existing API with the proposed NEW API.
+This change will NOT break existing API compatibility.
 
-Note: We could add the NEW API without changing the existing API. My concern with this approach is that it could cause confusion on which one to use and when.
- 
 == Test Plan ==