Changes between Version 1 and Version 2 of MapGuideRfc100

Timestamp:

09/03/10 05:19:41 (14 years ago)

Author:

jng

Comment:

--

MapGuideRfc100

@@ -9 +9 @@
 
 ||RFC Template Version||(1.0)||
-||Submission Date||(Date/Time submitted)||
-||Last Modified||Jackie Ng, 25 June 2010||
+||Submission Date||25 June 2010||
+||Last Modified||Jackie Ng, 3 September 2010||
 ||Author||Jackie Ng||
 ||RFC Status||draft||
@@ -64 +64 @@
 == Implications ==
 
-This is an API addition. Existing APIs are unaffected. As this is an addition to a PlatformBase API, other implementations of MgFeatureService (eg. AutoCAD Map3D Geospatial API) will have to implement these APIs as well.
+This is an API addition. Existing APIs are unaffected. As this is an addition to a PlatformBase API, other implementations of {{{MgFeatureService}}} (eg. AutoCAD Map3D Geospatial API) will have to implement these APIs as well.
+
+These APIs follow the same pattern as the {{{TestConnection}}} API in that only a return value of {{{true}}} will indicate validity. Anything else will result in a thrown FDO exception that gets bubbled up. Thus like the {{{TestConnection}}} API, callers should be testing filter/expression validity by testing for a return value of {{{true}}}
 
 == Test Plan ==