Changes between Version 16 and Version 17 of MapGuideRfc114


Ignore:
Timestamp:
07/01/11 00:32:26 (13 years ago)
Author:
samwang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc114

    v16 v17  
    7878
    7979Typically, the implementation of these API methods would forward the call request and parameters to corresponding FDO API.
    80 
    81 And also "!MgFeatureService" interface has to be updated to reflect this change:
    82 {{{
    83 class MG_PLATFORMBASE_API MgFeatureService : public MgService
    84 {
    85 INTERNAL_API:
    86 ......
    87 
    88     /// \brief
    89     ///  Create a save point in this transaction.
    90     ///
    91     /// \param suggestName
    92     /// Suggested save point name.
    93     ///
    94     /// \returns
    95     /// The actual name used
    96     virtual STRING AddSavePoint(CREFSTRING transactionID, CREFSTRING suggestName) = 0;
    97 
    98     /// \brief
    99     ///  Release a specific save point.
    100     ///
    101     /// \param savePointName
    102     /// Save point name.
    103     ///
    104     /// \returns
    105     /// Returns nothing
    106  
    107     virtual void ReleaseSavePoint(CREFSTRING transactionID, CREFSTRING savePointName) = 0;
    108    
    109     /// \brief
    110     ///  Rollback the transaction to a specified save point.
    111     ///
    112     /// \param savePointName
    113     /// Save point name.
    114     ///
    115     /// \returns
    116     /// Returns nothing
    117     virtual void RollbackSavePoint(CREFSTRING transactionID, CREFSTRING savePointName) = 0;
    118 ......
    119 }
    120 }}}
    121 
    12280== Implications ==
    12381This 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.