Changes between Version 7 and Version 8 of MapGuideRfc117

Timestamp:

Aug 19, 2011, 12:19:12 AM (13 years ago)

Author:

jng

Comment:

--

MapGuideRfc117

@@ -10 +10 @@
 ||RFC Template Version||(1.0)||
 ||Submission Date||20 June 2011||
-||Last Modified||20 June 2011||
+||Last Modified||19 August 2011||
 ||Author||Jackie Ng||
 ||RFC Status||ready for review||
 ||Implementation Status||pending||
-||Proposed Milestone||2.3||
+||Proposed Milestone||2.4||
 ||Assigned PSC guide(s)||(when determined)||
 ||'''Voting History'''||(vote date)||
@@ -41 +41 @@
 The MapGuide Platform API itself is already modular and abstract enough to have an implementation in MapGuide/AIMS and another implementation in AutoCAD Map3D. What would be really nice is to take the concepts from that presentation to its logical conclusion, into a separate '''desktop-based''' implementation of the MapGuide Platform API
 
+Having a desktop-based MapGuide API opens up a whole new class of mapping applications that can use the same data access, rendering and stylization available in MapGuide, but without needing connectivity to a local or remove MapGuide Server as all the functionality is now self contained. This makes for a suitable foundation for mobile and remote field mapping applications.
+
 == Proposed Solution ==
 
@@ -65 +67 @@
 MgFeatureService for the desktop is a thin wrapper around FDO. Each service API maps to its corresponding FDO command.
 
-MgResourceService for the desktop wraps a pre-defined directory on the native filesystem. Package loading is also implemented allowing for spatial data portability between a MapGuide Server and an application using the Desktop Platform API.
+MgResourceService for the desktop wraps a pre-defined directory on the native filesystem. Package loading is also implemented allowing for spatial data portability between a MapGuide Server and an application using the Desktop Platform API. Because it wraps the underlying filesystem and resource ids are mapped to file paths, resource ids are '''no longer case-sensitive''' for windows where file paths are not case-sensitive.
 
 MgMapBase, MgLayerBase and MgSelectionBase are near 1:1 copies of their MapGuide Server counterparts. Because the desktop implementation does not have to address http statelessness like the MapGuide Web API, the Open() and Save() and Create() methods of MgMapBase are not required and have been removed from the desktop implementation. 
@@ -71 +73 @@
 MgFeatureReader, MgDataReader and MgSqlDataReader wraps their respective FDO reader interfaces.
 
-This desktop implementation fulfils the data access (MgFeatureService) and rendering/stylization (MgRenderingService) requirements needed to build a functional desktop mapping application.
+This desktop implementation fulfills the data access (MgFeatureService) and rendering/stylization (MgRenderingService) requirements needed to build a functional desktop mapping application.
 
 This desktop implementation also includes a functional .net wrapper API, created via the existing SWIG infrastructure already present in the MapGuide source tree.
 
-Due to the tight dependency on server code, certain object caching and pooling mechanisms are omitted from the desktop implementation.
+Due to the tight dependency on server code, certain object caching and pooling mechanisms have been omitted from the desktop implementation.
 
 As 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:
 
  * Sessions
- * Map names
+ * Using the session repository to maintain runtime map state and selection
  * Authentication
  * Resource Security
@@ -149 +151 @@
    * GetSchemaMapping
 
+The following resource types are not utilised under the Desktop API:
+
+ * Web Layout
+ * Application Definition
+ * Print Layout
+
+The following functionality present already in MapGuide/AIMS, is not implemented or supported yet under the Desktop API:
+
+ * Feature Joins (SelectFeatures currently blindly assumes a non-extended feature class)
+ * Extended Feature Classes (these are currently skipped in a DescribeSchema operation)
+
 In 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.