Changes between Version 1 and Version 2 of MapGuideRfc70

Timestamp:

06/25/09 22:52:56 (16 years ago)

Author:

leaf

Comment:

--

MapGuideRfc70

@@ -8 +8 @@
 
 ||RFC Template Version||(1.0)||
-||Submission Date||June 23, 2009||
+||Submission Date||June 26, 2009||
 ||Last Modified||Leaf Li [[Timestamp]]||
 ||Author||Leaf Li||
@@ -24 +24 @@
 == Overview ==
 
-This proposal is to refactor MapGuide Web .NET API to some common dlls.
+This proposal is to extend MapGuide Feature Service to support applying schema.
 
 == Motivation ==
 
-Currently all MapGuide Web .NET API is in one single dll !MapGuieDotNetApi.dll, which includes Foundation, Geometry, !PlatformBase, !MapGuideCommon, !WebApp and !HttpHandler components. It isn’t good for users to reuse functionality provided by MapGuide Web .NET API. For example, users have to include a reference to all components even if they just want to use Geometry related API.
+Currently MapGuide Web API doesn’t support any functionality to create or modify schema of a feature source. The RFC is used to eliminate this limitation.
 
 == Proposed Solution ==
 
-MapGuide Web .NET API will be divided into five separated dlls. SWIG is used to create MapGuide .NET API as before.
- * OSGeo.!MapGuide.Foundation.dll: contains API in Foundation component.
- * OSGeo.!MapGuide.Geometry.dll: contains API in Geometry compoent.
- * OSGeo.!MapGuide.!PlatformBase.dll: contains API in !PlatformBase component.
- * OSGeo.!MapGuide.!MapGuideCommon.dll: contains API in !MapGuideCommon compoent.
- * OSGeo.!MapGuide.Web.dll: contains API in !WebApp and !HttpHandler components.
+ApplySchema need not only support adding, modifying but also support deleting schema elements. So we need a method to mark the schema element for deletion. The method Delete() will be added to classes MgFeatureSchema, MgClassDefinition, MgPropertyDefinition for it.
 
 == Implications ==
 
-Currently, there is no enough resources and funding to refator PHP and Java API. They may be implemented if resources and funding can be obtained in the future.
+This is new API only. There will be no effect on existing applications. However, API documentation need to be updated.
 
 == Test Plan ==
 
-Run the existing unit tests. No need to add new unit tests.
+Add unit tests for method MgFeatureService::ApplySchema into the existing Feature Service unit tests.
 
 == Funding/Resources ==