- From: Joseph Pecoraro <joepeck02@gmail.com>
- Date: Thu, 10 Dec 2009 14:45:34 -0500
- To: public-webapps@w3.org
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 Cheers, Joseph Pecoraro
Received on Thursday, 10 December 2009 19:46:14 UTC