Changes between Version 7 and Version 8 of MapGuideRfc107


Ignore:
Timestamp:
Jul 23, 2010, 2:19:49 AM (14 years ago)
Author:
yangte
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc107

    v7 v8  
    2424== Overview ==
    2525
    26 This RFC proposes to add a NEW !GetCapabilites() 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.
     26This 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.
    2727
    2828== 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.
    3129
    3230
     
    3836Existing API:
    3937{{{
    40     MgByteReader* GetCapabilities(CREFSTRING providerName);
     38    MgByteReader* GetTile(MgResourceIdentifier* mapDefinition,CREFSTRING baseMapLayerGroupName,INT32 tileColumn,INT32 tileRow,INT32 scaleIndex);
    4139}}}
    4240
    4341Proposed NEW API:
    4442{{{
    45     MgByteReader* GetCapabilities(CREFSTRING providerName, CREFSTRING connectionString);
     43    bool GenerateTile(MgResourceIdentifier* mapDefinition,CREFSTRING baseMapLayerGroupName,INT32 tileColumn,INT32 tileRow,INT32 scaleIndex);
    4644}}}
    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.
    4945
    5046== Implications ==