IETF Logo Mail Archive

Re: [Storagesync] Storagesync Digest, Vol 5, Issue 1

Markus Unterwaditzer <markus@unterwaditzer.net> Tue, 08 December 2015 18:59 UTC

Return-Path: <markus@unterwaditzer.net>
X-Original-To: storagesync@ietfa.amsl.com
Delivered-To: storagesync@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35991A1B5A for <storagesync@ietfa.amsl.com>; Tue, 8 Dec 2015 10:59:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level:
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wgDPkriLqQjx for <storagesync@ietfa.amsl.com>; Tue, 8 Dec 2015 10:59:28 -0800 (PST)
Received: from draco.uberspace.de (draco.uberspace.de [95.143.172.133]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2994F1A1B59 for <storagesync@ietf.org>; Tue, 8 Dec 2015 10:59:27 -0800 (PST)
Received: (qmail 3380 invoked from network); 8 Dec 2015 18:59:24 -0000
Received: from localhost (HELO localhost) (127.0.0.1) by draco.uberspace.de with SMTP; 8 Dec 2015 18:59:24 -0000
Date: Tue, 08 Dec 2015 19:59:22 +0100
From: Markus Unterwaditzer <markus@unterwaditzer.net>
To: Ted Lemon <mellon@fugue.com>
Message-ID: <20151208185922.GA9531@localhost.localdomain>
References: <1449452139832-4f314827-a7ecd596-c5312339@fugue.com> <1449454580239-1fd59d90-52f0231b-370f2ef5@gmail.com,> <> <1449455245871-cb7e86e1-1a0160c5-aa6acce3@fugue.com> <2015120711170621874681@bjtu.edu.cn> <1449459616112-6043cb32-cd69a1f9-1399f1c0@fugue.com> <CAO_Yprbct8wFbS1WFnZZENSp-OruRUk2nRyBv4tNeKv9_CGuCg@mail.gmail.com> <1449511062426-94cdee34-064ef498-327458b6@fugue.com> <CAO_YprZjqs_OFC3RybVvJ4GHWb3spKMMkkFTZO=YDustp825iw@mail.gmail.com> <1449593642163-c107ebb4-0f6d1c5a-a3f1c5e0@fugue.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND"
Content-Disposition: inline
In-Reply-To: <1449593642163-c107ebb4-0f6d1c5a-a3f1c5e0@fugue.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/ItW-U-3wb0V6a-jEkwJd7scC9Fs>
Cc: lh.sunlinh@gmail.com, storagesync@ietf.org
Subject: Re: [Storagesync] Storagesync Digest, Vol 5, Issue 1
X-BeenThere: storagesync@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mechanisms to synchronize client file systems with Internet-based data storage services <storagesync.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/storagesync>, <mailto:storagesync-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/storagesync/>
List-Post: <mailto:storagesync@ietf.org>
List-Help: <mailto:storagesync-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storagesync>, <mailto:storagesync-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2015 18:59:31 -0000

On Tue, Dec 08, 2015 at 04:54:01PM +0000, Ted Lemon wrote:
> Tuesday, Dec 8, 2015 4:06 AM Linhui Sun wrote:
> > That's better. It seems that a separate layer for conflict resolution is
> > well accepted. But for etag and versioning metadata, which to employ still
> > needs to be discussed. Any comments for that?
> 
> Both can be made to work in theory, but etag is missing explicit versioning,
> so in order to get conflict detection and avoid amnesiac servers erasing data
> on clients, you pretty much need to build up a metadata versioning system
> anyway.

Per-file conflicts can be detected with just etags. In the case of file-sync
this is often the only thing you can do, since conflict-resolution depends on
the filetype. Dropbox stores both copies in such cases. I'd say this is
reasonably efficient for average usecases.

Something like a three-way merge could also be done with just etags, but
doubles storage usage on the clientside.

> 
> 
> --
> Sent from Whiteout Mail - https://whiteout.io
> 
> My PGP key: https://keys.whiteout.io/mellon@fugue.com



> _______________________________________________
> Storagesync mailing list
> Storagesync@ietf.org
> https://www.ietf.org/mailman/listinfo/storagesync

v2.23.0 | Report a Bug | By Email