Changes between Version 35 and Version 36 of MapGuideRfc78

Timestamp:

Jul 24, 2009, 8:30:25 AM (15 years ago)

Author:

brucedechant

Comment:

--

MapGuideRfc78

@@ -145 +145 @@
 Timeout configuration for !MgTransaction
 
-As the transaction is a critical resource for database applications, a server-side transaction can be left open while the application is doing other things in between sql or even worse the application may fail or hang and the server would not know. So it needs to set a timeout for all transactions. If a transaction hasn't been committed or rollbacked within the timeout, the server will automatically rollback the transaction. If you call Commit() or Rollback() on the MgTransaction instance after timeout, an exception will be thrown reminding that the transaction has been timeout and reverted. 
+As the transaction is a critical resource for database applications, a server-side transaction can be left open while the application is doing other things in between sql or even worse the application may fail or hang and the server would not know. So it needs to set a timeout for all transactions. If a transaction hasn't been committed or rollbacked within the timeout, the server will automatically rollback the transaction. If you call Commit() or Rollback() on the !MgTransaction instance after timeout, an exception will be thrown reminding that the transaction has been timeout and reverted. 
 
 Two items will be added into serverconfig.ini for transaction timeout setting. If the transaction hasn't been committed or rollbacked within 6 minutes, it will be automatically rollbacked. 
@@ -154 +154 @@
 Bind !MgTransaction to FDO connection
 
-The transaction has to be bound with the underlying FDO connection where it starts during its life circle. The underlying FDO connection will be kept used by the transaction until the call of either Commit() or Rollback(). The implementation of MgTransaction should be able to return the underlying connection. 
+The transaction has to be bound with the underlying FDO connection where it starts during its life circle. The underlying FDO connection will be kept used by the transaction until the call of either Commit() or Rollback(). The implementation of !MgTransaction should be able to return the underlying connection. 
 
 == Implications ==