Re: Do we need transaction support in LDP? from Wilde, Erik on 2013-05-10 (public-ldp-wg@w3.org from May 2013)

From: Wilde, Erik <Erik.Wilde@emc.com>
Date: Thu, 9 May 2013 20:15:59 -0400
To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
CC: Kingsley Idehen <kidehen@openlinksw.com>
Message-ID: <CDB189D6.1149F%erik.wilde@emc.com>

On 2013-05-09 16:25 , "Kingsley Idehen" <kidehen@openlinksw.com> wrote:
>On 5/9/13 7:04 PM, Ashok Malhotra wrote:
>>On 5/9/2013 6:15 PM, Kingsley Idehen wrote:
>>> Leave it to the LDP compliant server to handle, ...
>> What's that?  Please define.Let the back-end (e.g., Oracle) handle ACID.

the problem is that if you interact with three collections, you have no
way to tell whether they are implemented against the same back-end, that
thus can guarantee transactions, or not. you either have to design
transactions into the interaction design (in the two general ways i
pointed out), or you have to live without it.

cheers,

dret.

Received on Friday, 10 May 2013 00:16:33 UTC