Changes between Version 1 and Version 2 of MapGuideRfc21


Ignore:
Timestamp:
05/30/07 10:10:05 (17 years ago)
Author:
brucedechant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc21

    v1 v2  
    88||RFC Template Version||(1.0)||
    99||Submission Date||May 7, 2007||
    10 ||Last Modified||Kenneth, GEOGRAF A/S [[Timestamp]]||
     10||Last Modified||Bruce Dechant [[Timestamp]]||
    1111||Author||Kenneth, GEOGRAF A/S||
    1212||RFC Status||draft||
    … …  
    2626== Motivation ==
    2727
    28 The map definition is Xml based, and easy to manipulate. The runtime map is in binary format, and tightly tied to the inner workings of the MapGuide server. It should be expected that the current format will change over time, thus breaking compatibility with external binary reader/writer applications.
     28The map definition is Xml based, and easy to manipulate. The runtime map is in binary format, and tightly tied to the inner workings of the !MapGuide server. It should be expected that the current format will change over time, thus breaking compatibility with external binary reader/writer applications.
    2929
    30 When using the current MapGuide API, the code for creating and maintaining the runtime map is found in code shared by the server and the API. This means that an application must be adapted to fit a specific version of the MapGuide server. Or at least have the correct version of the codebase (eg. dll's).
     30When using the current !MapGuide API, the code for creating and maintaining the runtime map is found in code shared by the server and the API. This means that an application must be adapted to fit a specific version of the !MapGuide server. Or at least have the correct version of the codebase (eg. dll's).
    3131
    3232== Proposed Solution ==
    3333
    3434There already exists code in the server to create a runtime map from a map defintion.
    35 There should be two more functions in the MgMap class:
     35There should be two more functions in the !MgMap class:
    3636{{{
    3737void MgMap::UpdateRuntimeMap(MgResourceService* resourceService, MgResourceIdentifier* mapDefinition, CREFSTRING mapName);
    … …  
    3939}}}
    4040
    41 The UpdateMapDefinition should just overwrite the mapDefinition with the current runtimemap.
    42 The UpdateRuntimeMap should try to sync the runtime map, by settings map properties. This will allow the current change-list scheme to work.
     41The !UpdateMapDefinition should just overwrite the mapDefinition with the current runtimemap.
     42The !UpdateRuntimeMap should try to sync the runtime map, by settings map properties. This will allow the current change-list scheme to work.
    4343
    44 These two functions should be exposed in the HttpHandler, along with the existing MgMap::CreateMap(...).
     44These two functions should be exposed in the !HttpHandler, along with the existing MgMap::!CreateMap(...).
    4545
    4646== Considerations ==
    … …  
    7777== Test Plan ==
    7878
    79 Write a small test application that calls the functions through the HttpHandler. Should be very easy to test.
     79Write a small test application that calls the functions through the !HttpHandler. Should be very easy to test.
    8080
    8181== Funding/Resources ==