Changes between Version 8 and Version 9 of MapGuideRfc90

Timestamp:

Nov 4, 2010, 1:27:48 AM (14 years ago)

Author:

uvlite

Comment:

--

MapGuideRfc90

@@ -9 +9 @@
 ||RFC Template Version||(1.0)||
 ||Submission Date||(Date/Time submitted)||
-||Last Modified||(your name here) [[Timestamp]]||
+||Last Modified|| Uv Nov 4 2010||
 ||Author||Zac Spitzer, Uv ||
 ||RFC Status||(draft)||
@@ -26 +26 @@
 
 With complex maps, it's more efficient to render one large tile than many small ones. 
-There is little or no benefit for simple maps like the Sheboygan Sample.[[BR]]
+There is little or no benefit for simple maps like the Sheboygan Sample.
 
 Using our 140 layer example map we can observe the following timing using metatilefactor 1 & 4
@@ -35 +35 @@
 Add a meta tile factor to the tile service, which then will render larger tiles enlarged by the provided factor.
 to be sliced up into the smaller tiles which then get served to clients.
-e.g.[[BR]]
+e.g.
+{{{
 Client -> GetTile(0,1) -> RenderMetaTile(0,0 - 1,1) -> SplitUp -> ReturnTile (0,1)
        -> GetTile(1,1) -> wait................................... ReturnTile (1,1)
-
+}}}
 == Issues ==
 
@@ -58 +59 @@
 == Test Plan ==
 
-The output of a tile map request should be identical whether served with meta tiling enabled or without. 
+The output of a tile map request has to be identical whether served with meta tiling enabled or without. 
 
 == Funding/Resources ==