Changes between Version 1 and Version 2 of Future/TileServiceEnhancements

Timestamp:

Mar 19, 2008, 12:05:50 AM (16 years ago)

Author:

zspitzer

Comment:

--

Future/TileServiceEnhancements

@@ -29 +29 @@
 and management of the tile caches. 
 
-= Cacheability Ideas =
+= Cacheability by HTTP =
 
 [wiki:MapGuideRfc11] added support for a '''Stateless Http GETTILEIMAGE request''', however, these tiles are served [[BR]]
 without any cache headers which means they can only be proxied using a custom 'aggressive' proxy service. [[BR]]
 
-[ticket:467 Add proper cache headers & file date to GETTILEIMAGE response] addresses this issue. 
+[ticket:467 Add proper cache headers & file date to GETTILEIMAGE response]. 
 
-Some of the issues to be resolved is how long to set the cache headers to cache the tiles before checking back [[BR]]
+One of the the issues to be resolved is how long to set the cache headers to cache the tiles before checking back [[BR]]
 to the Mapguide Server. This could done with a serverconfig.ini default and then an overriding parameter in the [[BR]]
-ResourceHeader.
+ResourceHeader. 
 
 = WMS =
 
-[ticket:286: WMS Cache headers] - see above.
+[ticket:286 WMS Cache headers] - see above.
 
-[ticket:285: Publish MapDefinitions via WMS] Currently only layers are exposed via WMS, maps should be as well.  
+[ticket:285 Publish MapDefinitions via WMS] Currently only layers are exposed via WMS, maps could be as well.  
 
 The WMS service doesn't currently use the tile cache, which means every WMS request is rendered. [[BR]]
@@ -51 +51 @@
 and capacity of WMS with Mapguide.[[BR]]
 
+= TMS = 
+
+[wiki:GoogleSoC2007#TileMapServicePublishing TMS]   
 
 
 
 
-