Changes between Version 2 and Version 3 of MapGuideRfc13

Timestamp:

Feb 8, 2007, 3:44:03 PM (17 years ago)

Author:

trevorwekel

Comment:

--

MapGuideRfc13

@@ -27 +27 @@
 == Motivation ==
 
-Currently, the MapGuide tile size is hard coded in the Server code and Ajax script as 300x300 pixels. For the purposes of performance tuning and to allow for alignment with 3rd party tile sets, it would be useful to set the tile size as a Server configuration parameter. However, this parameter would need to be exposed through the Web Extensions API so that the Ajax viewer is aware of the custom tile size.
+Currently, the !MapGuide tile size is hard coded in the Server code and Ajax script as 300x300 pixels. For the purposes of performance tuning and to allow for alignment with 3rd party tile sets, it would be useful to set the tile size as a Server configuration parameter. However, this parameter would need to be exposed through the Web Extensions API so that the Ajax viewer is aware of the custom tile size.
 
 Ideally, tile sizes should be associated with the map. However that will require changes to both the map definition and any authoring tools used to edit the map definition. Due to the impact of such a change, map definition based tile size is beyond the scope of this RFC. It would be appropriate to consider it in future work. 
@@ -39 +39 @@
 If not specified, the Server will default to 300x300.
 
-Add two additional APIs to MgTileService
+Add two additional APIs to !MgTileService
 INT32 GetTileSizeX();
 INT32 GetTileSizeY();
 
-Modify mapframe.php, mapframe.jsp, mapframe.aspx, and ajaxmappane.templ to pull the tile size from the MgTileService instead of simply hard coding the value. 
+Modify mapframe.php, mapframe.jsp, mapframe.aspx, and ajaxmappane.templ to pull the tile size from the !MgTileService instead of simply hard coding the value. 
 
 == Implications ==