You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Jim Waldo (JIRA)" <ji...@apache.org> on 2007/07/26 16:55:08 UTC
[jira] Created: (RIVER-55) Transaction spec could elaborate on
leasing semantics
Transaction spec could elaborate on leasing semantics
-----------------------------------------------------
Key: RIVER-55
URL: https://issues.apache.org/jira/browse/RIVER-55
Project: River
Issue Type: Improvement
Components: net_jini_core
Affects Versions: jtsk_2.1
Reporter: Jim Waldo
Priority: Minor
The entire transaction specification should be revisited with leasing issues in mind. Need to consider if there's a special case of leasing during the VOTING phase. There are instances where abort/cancel/expire are treated equally in the spec (esp. during the ACTIVE phase). I don't see why there needs to be a special case during the VOTING phase whereby the client or participant can abort the txn, but lease cancellation/expiration can't. Keeping the leasing semantics consistent up until the commit point (see TX2.8) seems to be the easiest and most intuitive way to explain and implement the spec.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.