Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of mueller@adobe.com designates
 64.18.1.185 as permitted sender)
From: Thomas Mueller <mueller@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Wed, 27 Jun 2012 14:58:51 +0100
Subject: Re: Native HTTP bindings for Oak
Thread-Topic: Native HTTP bindings for Oak
Thread-Index: Ac1UbP8wJXUn0XoEQIKpaJlX5xMTkg==
Message-ID: <CC10DD7A.2EDAD%mueller@adobe.com>
In-Reply-To: 
 <CAEWfVJ=g0zc+-qTsq10YggVmStNAZ1Te3+ebA=RYmHwqwKz+qA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.2.120421
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Betrand,

>FWIW, as a Sling user I agree that the "freeze my view of the
>repository for a while, whatever others are doing" feature looks like
>a useful one to expose over an Oak HTTP remoting layer.

Do you mean having a consistent snapshot of the data at a given point in
time? Yes, we want to support that using "revisions". Each read request
(getNodes) would contain a revision, and the result (when using the same
revision) would not change no matter what other clients modified.

But this feature is unrelated to the branch/merge / workspace feature that
Jukka proposed here (at least as far as I understand).

Regards,
Thomas