Changes between Version 5 and Version 6 of MapGuideRfc30


Ignore:
Timestamp:
Aug 27, 2007, 9:24:50 PM (15 years ago)
Author:
leaf
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc30

    v5 v6  
    4242 * Previously, !MgSpatialContextData is an internal class of !MapGuide Web API, which is used to represent all information of a FDO spatial context. In this RFC, it will be extended and exposed so that users can use it add spatial context into configuration.
    4343 * There isn’t a class existing to represent spatial context collection. So !MgSpatialContextDataCollection will be added, which is just a collection of !MgSpatialContextData. !MgConfigDocument uses it to maintain all spatial contexts of all feature classes.
    44  * !MgConfigDocument maintains three collections, schema collection, physical schema mapping collection, and spatial context collection. These three collections will provide all information to create configuration XML. So it generates configuration XML string or file only when MgConfigDocument::ToXML is called. MgConfigDocument doesn’t provide any functions to add schema mapping. So it is derived classes’ responsibility to populate schema mapping information into schema mapping collection.
     44 * !MgConfigDocument maintains three collections, schema collection, physical schema mapping collection, and spatial context collection. These three collections will provide all information to create configuration XML. So it generates configuration XML string or file only when MgConfigDocument::ToXML is called. !MgConfigDocument doesn’t provide any functions to add schema mapping. So it is derived classes’ responsibility to populate schema mapping information into schema mapping collection.
    4545 * !MgRfpConfigDocument, !MgWmsConfigDocument and !MgOdbcConfigDocument are derived from !MgConfigDocument. They implement a method !AddOverrideInfo to add feature class definitions and their physical mappings into configuration.
    4646
     
    6666== Implications ==
    6767
    68 Backwards compatibility should be maintained since ConfigDocument is just a utility based on existing MapGuide Web API and FDO and will not break any existing applications. Documentation will need to be updated for the new functionality.
     68Backwards compatibility should be maintained since !ConfigDocument is just a utility based on existing !MapGuide Web API and FDO and will not break any existing applications. Documentation will need to be updated for the new functionality.
    6969
    7070== Test Plan ==