W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: [DataCache] CacheTransaction missing committed state

From: Nikunj R. Mehta <nikunj.mehta@oracle.com>
Date: Wed, 16 Dec 2009 18:18:59 -0800
Cc: public-webapps@w3.org
Message-Id: <C872F9CE-3420-4297-B932-A175400F1325@oracle.com>
To: Joseph Pecoraro <joepeck02@gmail.com>

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
Received on Thursday, 17 December 2009 02:20:19 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:35 GMT