Changes between Version 1 and Version 2 of MapGuideRfc56


Ignore:
Timestamp:
Oct 6, 2008, 9:07:45 AM (14 years ago)
Author:
chrisclaydon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc56

    v1 v2  
    1 Placeholder
     1= !MapGuide RFC 56 - Add additional map commands to GETDYNAMICMAPOVERLAYIMAGE=
     2
     3This page contains an change request (RFC) for the !MapGuide Open Source project.
     4More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
     5
     6
     7== Status ==
     8
     9||RFC Template Version||(1.0)||
     10||Submission Date||October 6, 2008||
     11||Last Modified||Chris Claydon [[Timestamp]]||
     12||Author||Chris Claydon||
     13||RFC Status||('''draft''', proposed, frozen for vote, adopted, retracted, or rejected)||
     14||Implementation Status||('''pending''', under development, completed)||
     15||Proposed Milestone||2.1||
     16||Assigned PSC guide(s)||(when determined)||
     17||'''Voting History'''||(vote date)||
     18||no vote|| ||
     19
     20== Overview ==
     21
     22The proposal is to add additional, optional parameters to the GETDYNAMICMAPOVERLAYIMAGE HTTP request format to allow setting the map view state. These parameters are already supported by the GETVISIBLEMAPEXTENT and GETMAPIMAGE HTTP request formats.
     23
     24== Motivation ==
     25
     26The MGOS AJAX and Fusion viewers currently make (at least) two HTTP requests to render each new map image - one to GETVISIBLEMAPEXTENTS, which is used to set the current map view, and one to GETDYNAMICMAPOVERLAYIMAGE. The first request returns the extents of the map after the view state parameters have been applied. But in some cases this information is not required, and the two calls could easily be combined into one. This would provide increased efficiency and scalability.
     27
     28== Proposed Solution ==
     29
     30The proposal is to add support for the following parameters to the GETDYNAMICMAPOVERLAYIMAGE HTTP request format:
     31
     32||SETDISPLAYDPI||
     33||SETDISPLAYWIDTH||
     34||SETDISPLAYHEIGHT||
     35||SETVIEWSCALE||
     36||SETVIEWCENTERX||
     37||SETVIEWCENTERY||
     38||CLIENTAGENT||
     39||SHOWGROUPS||
     40||HIDEGROUPS||
     41||SHOWLAYERS||
     42||HIDELAYERS||
     43
     44== Implications ==
     45
     46This section allows discussion of the repercussions of the change, such as whether there will be any breakage in backwards compatibility, if documentation will need to be updated, etc.
     47
     48== Test Plan ==
     49
     50How the proposed change will be tested, if applicable.  New unit tests should be detailed here???
     51
     52== Funding/Resources ==
     53
     54This section will confirm that the proposed feature has enough support to proceed.  This would typically mean that the entity making the changes would put forward the RFC, but a non-developer could act as an RFC author if they are sure they have the funding to cover the change.