Changes between Version 7 and Version 8 of Future/TileServiceEnhancements

Timestamp:

05/29/14 20:10:55 (11 years ago)

Author:

jng

Comment:

--

Future/TileServiceEnhancements

@@ -383 +383 @@
     ///
     virtual void UnlockCache(MgResourceIdentiifer* tileSetDefinition);
+
+    /// Returns the default width of a tile
+    ///
+    virtual INT32 GetDefaultTileSizeX(MgResourceIdentiifer* tileSetDefinition);
+
+    /// Returns the default height of a tile
+    ///
+    virtual INT32 GetDefaultTileSizeY(MgResourceIdentiifer* tileSetDefinition);
+
+    /// Returns the list of available tile providers, along with supported connection parameters
+    ///
+    virtual MgByteReader* GetTileProviders();
 };
 }}}
@@ -407 +419 @@
     virtual void UnlockCache(MgResourceIdentiifer* tileSetDefinition);
 
+    /// Returns the default width of a tile
+    ///
+    virtual INT32 GetDefaultTileSizeX(MgResourceIdentiifer* tileSetDefinition);
+
+    /// Returns the default height of a tile
+    ///
+    virtual INT32 GetDefaultTileSizeY(MgResourceIdentiifer* tileSetDefinition);
+
+    /// Returns the list of available tile providers, along with supported connection parameters
+    ///
+    virtual MgByteReader* GetTileProviders();
+
     /// Returns the timestamp of when the tile for the specified map/group/row/col/scale was generated. Returns NULL if no such tile exists
     ///
@@ -420 +444 @@
 
 Notice that no new GetTile overload is introduced (assuming this feature is separate from the HTTP 304 cacheability support). This is because tile access requires the same set of parameters, except that instead of a Map Definition, we can specify a TileSetDefinition instead. On the implementation side, the GetTile methods need to support TileSetDefinition as a valid resource type and be able to resolve the physical tile storage location to fetch and store tiles in from the TileSetDefinition. For a first cut implementation, it is safe to just hard-code this logic to resolve to the same physical tile cache directory that the existing MapGuide tile cache code uses.
+
+The GetTileProviders method is akin to GetFeatureProviders in MgFeatureService. It is a method to assist client-side authoring tools to provide rich user interfaces for editing TileSet Definitions. A sample response looks like this:
+
+{{{
+<?xml version="1.0" encoding="UTF-8"?>
+<TileProviderList>
+  <TileProvider>
+    <Name>Default</Name>
+    <DisplayName>Default Tile Provider</DisplayName>
+    <Description>Default tile access provided by MapGuide. Supports MapGuide-managed tile path or user-defined path</Description>
+    <ConnectionProperties>
+      <ConnectionProperty Enumerable="false" Protected="false" Required="true">
+        <Name>TilePath</Name>
+        <LocalizedName>TilePath</LocalizedName>
+        <DefaultValue>%MG_TILE_CACHE_PATH%</DefaultValue>
+      </ConnectionProperty>
+  </TileProvider>
+</TileProviderList>
+}}}
 
 == Tile Set Locking ==