Changes between Version 2 and Version 3 of MapGuideRfc170


Ignore:
Timestamp:
Apr 24, 2019, 6:21:46 PM (5 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc170

    v2 v3  
    5555=== Configurable TileExtentOffset ===
    5656
    57 In addition to meta-tiling parameters, the (previously-global) {{{TileExtentOffset}}} server configuration property is now available as a tileset-specific parameter.
     57The (previously-global) {{{TileExtentOffset}}} server configuration property is now available as a tileset-specific parameter.
    5858
    5959=== Meta-tiling ===
    … …  
    189189These new overloads are designated {{{EXTERNAL_API}}} because meta-tiles are not intended to be consumed by regular MapGuide applications. They are raw image frame buffers that the rendering infrastructure will use to sub-divide back into tiles of the original requested size. But at the same time, these overloads have to be present in the {{{MgRenderingService}}} contract to allow a server-based tile service to still request meta-tiles through a proxy instance (should a server-based instance not be available) hence the {{{EXTERNAL_API}}} designation.
    190190
     191If applications do take advantage of these new overloads, it is expected they will always pass a {{{metaTilingFactor}}} of {{{0}}} when calling these new overloads or they know how to process and sub-divide the raw image frame buffer back into tile images of the original tile size.
     192
    191193Meta-tiling support will be surfaced via new tile set definition parameters:
    192194