I-D on transactions

Rohit Khare (khare@w3.org)
Wed, 6 Nov 1996 12:58:44 -0500

[Adam flagged this -- RK]

On my first scan, it looks like an interesting proposal, but its strength
and weakness is its singleminded focus on transactions. I can see it being
implemented as HTTP as well; the transaction id is a URI, and subtasks POST
back success or failure to it; and GET is a blocking wait that returns only
when comiitted or aborted.


A New Internet-Draft is available from the on-line Internet-Drafts

Title : Transaction Internet Protocol

Author(s) : J. Lyon
Filename : draft-lyon-itp-nodes-00.txt
Pages : 12
Date : 11/05/1996

In many applications where different nodes cooperate on some work,
there is
a need to guarantee that the work happens atomically. that is,
each node
must reach the same conclusion as to whether the work is to be
even in the face of failures. This document proposes a simple,
easily-implemented protocol for achieving this end.