Changes between Version 13 and Version 14 of MapGuideRfc78

Timestamp:

Jul 9, 2009, 11:40:10 PM (15 years ago)

Author:

klain

Comment:

--

MapGuideRfc78

@@ -109 +109 @@
 }}}
 
+Timeout configuration for MgTransaction
+
+If an MgTransaction has been started but hasn't been committed or rollbacked within the timeout, the transaction will be automatically rollbacked. If you call Commit() or Rollback() after timeout, an exception will be thrown reminding that the transaction has been timeout. 
+
+Bind MgTransaction to FDO connection
+
+The transaction has to be bound with the underlying FDO connection where it starts from during its life circle. The underlying FDO connection will be kept used by the transaction until the call of either Commit() or Rollback(). 
 
 == Implications ==
 
-This section allows discussion of the repercussions of the change, such as whether there will be any breakage in backwards compatibility, if documentation will need to be updated, etc.
+This is the 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. 
+
+As noted in the above example, if you use it along with UpdateFeatures(), additional attention should be paid not to pass in true for useTransaction. Otherwise, it will incur a nested transaction which is currently not supported by FDO. 
 
 == Test Plan ==
 
-How the proposed change will be tested, if applicable.  New unit tests should be detailed here???
+A new unit test similar to the above example will be added into the existing Feature Service unit tests. 
 
 == Funding/Resources ==
 
-This section will confirm that the proposed feature has enough support to proceed.  This would typically mean that the entity making the changes would put forward the RFC, but a non-developer could act as an RFC author if they are sure they have the funding to cover the change.
+Supplied by Autodesk.