Changes between Version 9 and Version 10 of MapGuideRfc126


Ignore:
Timestamp:
May 6, 2013, 3:53:40 AM (11 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc126

    v9 v10  
    369369[[Image(AjaxViewerAfter.PNG)]]
    370370
     371For browsers that don't support data URIs, there will be an additional GETDYNAMICMAPOVERLAYIMAGE request.t
     372
    371373And the Fusion Viewer request chain for a single selection looks like this:
    372374
    … …  
    379381Similarly, the request to SaveSelection.php may not even be needed either as QUERYMAPFEATURES supports selection set persistence.
    380382
    381 Such changes however, are not within the scope of this RFC.
     383Such changes however, are not within the scope of this RFC and is left as a post-RFC implementation exercise.
     384
     385This RFC has already been implemented in their respective [http://trac.osgeo.org/mapguide/browser/sandbox/jng/queryfeatures_v2 MapGuide] and [http://trac.osgeo.org/fusion/browser/sandbox/queryfeatures_v2 Fusion] sandboxes. Upon adoption of this RFC, both sandboxes will be merged into their respective trunk streams.
    382386
    383387== Implications ==