Changes between Version 18 and Version 19 of MapGuideRfc107

Timestamp:

07/25/10 02:47:53 (14 years ago)

Author:

yangte

Comment:

--

MapGuideRfc107

@@ -24 +24 @@
 == Overview ==
 
-This RFC proposes to add a NEW !GenerateTile() API to the tile service which return a bool value to indicate the tile generate success or not. This function will generate the tile on the server but not get the image from server. This function will allow user to pre-cache tiles on the server but elimate the cost of image transfer.
+This RFC proposes to add a NEW !GenerateTile() API to the tile service. This new API will generate the tile on the server but not get the image from server.
 
 == Motivation ==
+MapGuide users want to allow easy pre-seeding of base map tiles, for example, to generate all the tiles of a map at one time, now they can call the API GetTile:
 
+Existing API:
+{{{
+    MgByteReader* GetTile(MgResourceIdentifier* mapDefinition,CREFSTRING baseMapLayerGroupName,INT32 tileColumn,INT32 tileRow,INT32 scaleIndex);
+}}} 
+
+There's one problem with this existing API, suppose the user run a tool(like Maestro MgCooker) on the client PC to generate all the tiles of a map, the client will get the tile image from the server.
+Actually the user just want to generate the tiles on the server to make the rendering/navigation of a map more smooth. But the transfer of the tile image will increase the cost to finish this job(usually thousands of tiles will be generate).
+So this RFC want to add a NEW API !GenerateTile() which generate the tile on the server and return a bool value.