Changes between Version 16 and Version 17 of MapGuideRfc117


Ignore:
Timestamp:
10/03/11 20:25:57 (13 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc117

    v16 v17  
    8989As already mentioned, the desktop implementation does not have to address http statelessness like the MapGuide Web API, as such certain concepts no longer apply when moving to the desktop:
    9090
    91  * Sessions
     91 * Session Expiry - Session repositories still exist as a storage mechanism for transient resources, but session cleanup is now a manual action and not one that is automatically performed at certain intervals, thus there is no longer a need to keep a session "alive" as you would in a normal MapGuide Web Application
    9292 * Using the session repository to maintain runtime map state and selection
    9393 * Authentication
    … …  
    229229== Implications ==
    230230
    231 Like AutoCAD Map3D, certain aspects of the Platform API does not translate cleanly from the MapGuide Server context. As such the following functionality is currently not implemented (and throws MgNotImplementedException when invoked).
     231Like AutoCAD Map3D, certain aspects of the Platform API does not translate cleanly from the MapGuide Server context or are no longer applicable. As such the following functionality is currently not implemented (and throws MgNotImplementedException when invoked).
    232232
    233233 * MgResourceService
    … …  
    242242   * GetRepositoryHeader
    243243   * EnumerateReferences
    244    * EnumerateUnmanagedData
    245244
    246245 * MgFeatureService
    247    * ExecuteSqlQuery (version that supports parameters/transactions)
    248    * ExecuteSqlNonQuery (version that supports parameters/transactions)
    249246   * DescribeWfsFeatureType
    250247   * GetWfsFeature
    … …  
    254251 * Web Layout
    255252 * Application Definition
    256  * Print Layout
    257253
    258254Other features that are not yet fully implemented, tested or incomplete:
    259255
    260256 * MgTransaction support
    261  * Aliases
    262257
    263258In terms of compatibility, existing MapGuide application code is compatible at the source code level provided the code is targeting the subset of the MapGuide API that is supported and implemented by this desktop API.