Changes between Version 6 and Version 7 of MapGuideRfc134


Ignore:
Timestamp:
May 17, 2013, 8:15:51 AM (11 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc134

    v6 v7  
    176176JSON output format is supported, and provides the same benefits as other operations that support JSON output.
    177177
    178 As part of this RFC, Fusion will be modified use CREATERUNTIMEMAP for its map initialization if it determined that the server support is there, allowing it to bypass the asynchronous call chain to LoadMap.php and LoadScaleRanges.php. Based on tests against various maps of various sizes, CREATERUNTIMEMAP beats the LoadMap.php/LoadScaleRanges.php combination in both response size and time/latency, with only small additional client-side overhead in re-shaping the CREATERUNTIMEMAP response to suit the existing Fusion map initialization code.
     178As part of this RFC, Fusion will be modified use CREATERUNTIMEMAP for its map initialization if it determined that the server support is there, allowing it to bypass the asynchronous call chain to LoadMap.php and LoadScaleRanges.php. Based on tests against various maps of various sizes, CREATERUNTIMEMAP beats the LoadMap.php/LoadScaleRanges.php combination in both response size and time/latency (and these performance gains increase with map size!), with only small additional client-side overhead in re-shaping the CREATERUNTIMEMAP response to suit the existing Fusion map initialization code.
    179179
    180180Some example responses below (all using the Sheboygan Map Definition):