| 1 | | 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. |
| | 1 | Currently if you move or rename a 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 you move or rename a !FeatureSource, the !LayerDefinitions which reference to this !FeatureSource are not updated to use the new !FeatureSource URL, and thus fail to work properly. RFC 74 overloads the !ResourceService API !MoveResource by adding a new parameter "bool cascade" to indicate whether to update the referencing resources or not. The old API will continue to exist along with the new API to keep backwards compatibility. |
