On Dec 10, 2009, at 11:45 AM, Joseph Pecoraro wrote:
The specification does not say when a CacheTransaction's status
changes to committed. This should be a trivial addition.
- 4.2.2. Constructing and modifying data caches
http://dev.w3.org/2006/webapi/DataCache/#transaction-status
The spec outlines three states of a CacheTransaction:
[[ Each cache transaction has a status, which can be either of
pending, committed, or aborted. ]]
Pending and Aborted states are handled (the last step in each
appropriate section):
- Starting a Transaction: set as pending
- Abort a Transaction: set as aborted
- Online Capture Failure: set as aborted
I would expect the status to be set as committed as the last step in
the "Complete a Transaction":
http://dev.w3.org/2006/webapi/DataCache/#complete-transaction
That would add the following to the list:
- Complete a Transaction: set as committed
I added this as the last step in the steps to commit a transaction.
Nikunj
http://o-micron.blogspot.com
