Changes between Version 1 and Version 2 of MapGuideRfc38


Ignore:
Timestamp:
Oct 2, 2007, 3:40:41 PM (17 years ago)
Author:
trevorwekel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc38

    v1 v2  
    1 = !MapGuide RFC 38 - GETDYNAMICMAPOVERLAY Enhancements for Selection =
     1= !MapGuide RFC 38 - GETDYNAMICMAPOVERLAYIMAGE Enhancements for Selection =
    22
    33This page contains an change request (RFC) for the !MapGuide Open Source project. 
    … …  
    2323== Overview ==
    2424
    25 Enhance the GETDYNAMICMAPOVERLAY HTTP API to allow the selection and overlay images to be rendered as separate images.
     25Enhance the GETDYNAMICMAPOVERLAYIMAGE HTTP API to allow the selection and overlay images to be rendered as separate images.
    2626
    2727== Motivation ==
    … …  
    3131== Proposed Solution ==
    3232
     33Add an additional parameter BEHAVIOR to the existing GETDYNAMICMAPOVERLAYIMAGE. Increase the VERSION to 2.0.0 and deprecate the existing KEEPSELECTION parameter for the new version of the API.  BEHAVIOR is a bitmask with the following values:
     34
     35{{{
     36  RenderSelection = 1
     37  RenderLayers = 2
     38  KeepSelection = 4
     39}}
     40
     41Add an additional signature for !MgRenderingService.!RenderDynamicMapOverlay that includes the behavior parameter:
     42
     43{{{
     44  MgByteReader* RenderDynamicOverlay(MgMap* map, MgSelection* selection, CREFSTRING format, INT32 behavior);
     45}}}
     46
     47Update the existing !WebLayout based ajax viewer to use the new API.  This will have no performance benefit since the viewer will call the new API specifying both !RenderSelection and !RenderLayers.
    3348
    3449== Implications ==
    3550
    36 
     51Since this is a new version of the HTTP request and a new signature for RenderDynamicMapOverlay, compatibility with existing clients/scripts is maintained.  The behavior parameter encapsulates the current "keepSelection" functionality so the existing RenderDynamicOverlay methods could be deprecated in a future release.
    3752
    3853== Test Plan ==
    3954
    40 
     55Ensure that existing clients continue to function as expected.  Verify that the new HTTP API renders only the selection or layers, or both depending on the behavior setting. 
    4156
    4257== Funding/Resources ==
    4358
    44 Autodesk
     59Autodesk.  Selection improvements for the new "Fusion" based viewer are TBD.
     60