Changes between Version 2 and Version 3 of FdoClientUtilities


Ignore:
Timestamp:
Jan 3, 2010, 6:37:42 PM (14 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FdoClientUtilities

    v2 v3  
    1414
    1515 3. Functions that can be used by provider writers. E.g. expression evaluation. Providers can incorporate added functionality by reusing common components.
     16
     17 4. The !MapGuide Platform API
    1618
    1719The three options are fairly different in terms of what typically would be supported by each, but there is some potential overlap. Projection support is one that could be added via any of these mechanisms.
    … …  
    7375Cons:
    7476 * Shared functions have to be written in a very generic way.
     77
     78== 4. The !MapGuide Platform API ==
     79
     80A combination of 1) and 2) already exists, in the form of the !MapGuide Platform API.
     81
     82The !MapGuide Platform API already exposes most of what the FDO API has to offer, and provides the additional services/capabilities desired in a client layer:
     83 * Coordinate System Transformation (offered by !MgCoordinateSystem API)
     84 * Built-in support for joins (offered by !GwsQueryEngine)
     85 * Pluggable rendering/stylization
     86
     87Pros:
     88 * Offers an already rich and solid foundation.
     89 * All the pros of 1) and 2)
     90 * !MapGuide Developers can already leverage such an API
     91
     92Cons:
     93 * Currently bound to the !MapGuide Server/Web tiers. A [http://trac.osgeo.org/mapguide/wiki/Future/DesktopSdk desktop-based] implementation is required.