Changes between Version 2 and Version 3 of MapGuideRfc74

Timestamp:

Aug 11, 2009, 1:10:51 AM (15 years ago)

Author:

christinebao

Comment:

--

MapGuideRfc74

@@ -24 +24 @@
 == Overview ==
 
-This RFC changes the ResourceService API MoveResource to avoid breaking links.
+This RFC adds a new API to ResourceService, overloading MoveResource to avoid breaking links.
 
 == Motivation ==
 
-Currently if move or rename resource, the other resources referencing to it are not updated and can't find the new location of the resource, thus they will not work anymore. For example, if move or rename a FeatureSource, the LayerDefinitions which reference to this FeatureSource are not updated to use the new FeatureSource URL, and they can't work properly.
-This RFC modifies the ResourceService API MoveResource, adding a new parameter "bool cascade" to indicate whether update the referencing resources or not.
+Currently if move or rename resource, the other resources referencing to it are not updated and can't find the new location of the resource, thus they will not work anymore. For example, if move or rename a FeatureSource, the LayerDefinitions which references to this FeatureSource are not updated to use the new FeatureSource URL, and they can't work properly.
+This RFC overload the ResourceService API MoveResource, adding a new parameter "bool cascade" to indicate whether update the referencing resources or not. The old API exist along with the new API to keep compatible.
 
 == Proposed Solution ==
@@ -136 +136 @@
 == Implications ==
 
-After changing this API all the related applications should be updated.
+This new added API won't affect existing application.
 
 == Test Plan ==