Changes between Version 2 and Version 3 of MapGuideRfc74


Ignore:
Timestamp:
08/11/09 01:10:51 (15 years ago)
Author:
christinebao
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc74

    v2 v3  
    2424== Overview ==
    2525
    26 This RFC changes the ResourceService API MoveResource to avoid breaking links.
     26This RFC adds a new API to ResourceService, overloading MoveResource to avoid breaking links.
    2727
    2828== Motivation ==
    2929
    30 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.
    31 This RFC modifies the ResourceService API MoveResource, adding a new parameter "bool cascade" to indicate whether update the referencing resources or not.
     30Currently 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.
     31This 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.
    3232
    3333== Proposed Solution ==
     
    136136== Implications ==
    137137
    138 After changing this API all the related applications should be updated.
     138This new added API won't affect existing application.
    139139
    140140== Test Plan ==