Changes between Version 11 and Version 12 of MapGuideRfc114

Timestamp:

07/01/11 00:23:40 (13 years ago)

Author:

samwang

Comment:

--

MapGuideRfc114

@@ -79 +79 @@
 Typically, the implementation of these API methods would forward the call request and parameters to corresponding FDO API.
 
+And also MgFeatureService has to be updated to reflect this change:
+{{{
+class MG_PLATFORMBASE_API MgFeatureService : public MgService
+{
+PUBLISHED_API:
+......
+
+    /// \brief
+    ///  Create a save point in this transaction.
+    /// 
+    /// \param suggestName
+    /// Suggested save point name.
+    /// 
+    /// \returns 
+    /// The actual name used
+    virtual STRING AddSavePoint(CREFSTRING transactionID, CREFSTRING suggestName) = 0;
+
+    /// \brief
+    ///  Release a specific save point.
+    /// 
+    /// \param savePointName 
+    /// Save point name.
+    /// 
+    /// \returns 
+    /// Returns nothing
+ 
+    virtual void ReleaseSavePoint(CREFSTRING transactionID, CREFSTRING savePointName) = 0;
+    
+    /// \brief
+    ///  Rollback the transaction to a specified save point.
+    /// 
+    /// \param savePointName 
+    /// Save point name.
+    /// 
+    /// \returns 
+    /// Returns nothing 
+    virtual void RollbackSavePoint(CREFSTRING transactionID, CREFSTRING savePointName) = 0;
+......
+}
+}}}
+
 == Implications ==
 This is a new API, so API documentation need to be updated. However, it will not affect the existing application if you don't use it at all.