Changes between Version 7 and Version 8 of MapGuideRfc107
- Timestamp:
- 07/23/10 02:19:49 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapGuideRfc107
v7 v8 24 24 == Overview == 25 25 26 This RFC proposes to add a NEW !Ge tCapabilites() API to the feature service which contains an additional connection string parameter. This will primarily allow for acquiring the "runtime" capabilities of WFS/WMS providers.26 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. 27 27 28 28 == Motivation == 29 30 The existing Feature service !GetCapabilties() API works correctly for most providers, but fails to return the true capabilities of the server connected to by a WFS/WMS provider because there is no way to specify the connection string containing the server.31 29 32 30 … … 38 36 Existing API: 39 37 {{{ 40 MgByteReader* Get Capabilities(CREFSTRING providerName);38 MgByteReader* GetTile(MgResourceIdentifier* mapDefinition,CREFSTRING baseMapLayerGroupName,INT32 tileColumn,INT32 tileRow,INT32 scaleIndex); 41 39 }}} 42 40 43 41 Proposed NEW API: 44 42 {{{ 45 MgByteReader* GetCapabilities(CREFSTRING providerName, CREFSTRING connectionString);43 bool GenerateTile(MgResourceIdentifier* mapDefinition,CREFSTRING baseMapLayerGroupName,INT32 tileColumn,INT32 tileRow,INT32 scaleIndex); 46 44 }}} 47 48 Note: This NEW API will behave exactly the same as the old API if it is given an empty string as the connection string parameter.49 45 50 46 == Implications ==