IETF Logo Mail Archive

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

Linhui Sun <lh.sunlinh@gmail.com> Mon, 07 December 2015 02:16 UTC

Return-Path: <lh.sunlinh@gmail.com>
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 5B7A01AC3D3 for <storagesync@ietfa.amsl.com>; Sun, 6 Dec 2015 18:16:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 PrRhohDYuenx for <storagesync@ietfa.amsl.com>; Sun, 6 Dec 2015 18:16:22 -0800 (PST)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 545271AC3CF for <storagesync@ietf.org>; Sun, 6 Dec 2015 18:16:22 -0800 (PST)
Received: by qgcc31 with SMTP id c31so133332911qgc.3 for <storagesync@ietf.org>; Sun, 06 Dec 2015 18:16:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:from:to:cc:in-reply-to:references:subject:date :message-id:mime-version; bh=WsLrVpLbIXXnMwaIrUkus2jqxBnpThmykJI78YTrQ/E=; b=q3Zkj5Sr4pYqX50Hf3QQVEQ34smpTC5IiuuqB54xFWgRPxCOK5UAsHaQS14pIC5PGi YNKsjfCVhRJuLlV0tYC1isIIwMSlvsstpH8e5QgLEscs1q/wFDZLVmT2udYzmIt4EGy/ dWLw6V5r3PEJ3Meo6oU/riFGdTxBPpAjnKAmskhTWBEtSTXpRs5QBYuB/Eg3vLZz1wzj KuNQKkYY4orkNSse6H3dA4+bpTW1k+7FwzXXXLtTZEaVpRk6mLwQ8zk0Z0p08x5656M/ Im1DifH0z9cXH1ugUItKOCDNGcf85LFPZvgeGdF4ahoV73btWpaTBY2VyijXvMPjPkQq Fo+g==
X-Received: by 10.140.217.211 with SMTP id n202mr36142076qhb.26.1449454581618; Sun, 06 Dec 2015 18:16:21 -0800 (PST)
Received: from [127.0.0.1] (ec2-54-210-254-233.compute-1.amazonaws.com. [54.210.254.233]) by smtp.gmail.com with ESMTPSA id u59sm10720090qge.0.2015.12.06.18.16.20 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 06 Dec 2015 18:16:20 -0800 (PST)
Content-Type: multipart/alternative; boundary="----sinikael-?=_1-14494545799720.6955633715260774"
From: Linhui Sun <lh.sunlinh@gmail.com>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <1449452139832-4f314827-a7ecd596-c5312339@fugue.com>
References: <20151204181110.GA2418@localhost.localdomain> <1449255654746-36498631-5591108f-793d865a@fugue.com> <8F085EBA-F6A4-4FBD-8B8E-1F9AE114FD05@unterwaditzer.net> <CAO_YpraJsDKbOXD9MdxHqeAYTMoiZFyViHX+P2PtD=9hpRz9MQ@mail.gmail.com> <20151206173646.GA6290@localhost.localdomain> <1449447450498-61af5a96-1c461047-3019ac1e@gmail.com> <20151207002020.GA5002@localhost.localdomain> <1449448362292-7d42d496-109559e8-4177b3f9@gmail.com> <20151207003810.GA24130@localhost.localdomain> <1449449404474-72724227-c54ecf87-7d18f3b0@gmail.com> <20151207005426.GA29483@localhost.localdomain> <CAO_YpramyzAZ8hS6aphmBNw2FiKTpesb9uW7uGHtjRH_YkPAJg@mail.gmail.com> <1449452139832-4f314827-a7ecd596-c5312339@fugue.com>
Date: Mon, 07 Dec 2015 10:16:17 +0800
X-Cm-Message-Id: 1449454579807462ae3914fb36c97c4e8595adc2eb26c08f5664ebf3c52e2933383508
X-Cm-Draft-Id: WyJhIiwzLCJkcmFmdF9pZCIsIjE0NDk0NTQ1NzcwMDAiLCJjIiwiMTUxOTM5MTI5MTk2ODkzMDAyMCIsInYiLDFd
X-Mailer: CloudMagic
Message-Id: <1449454580239-1fd59d90-52f0231b-370f2ef5@gmail.com>
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/snPl-Wsi6hhF4BsxQTWOioXT5O4>
Cc: 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: Mon, 07 Dec 2015 02:16:24 -0000

On 周一, 12月 7, 2015 at 09:35, Ted Lemon <mellon@fugue.com> wrote:
Sunday, Dec 6, 2015 8:09 PM Linhui Sun wrote:
>> Those are sync conflicts, how to deal with then depends on the kind of
>> data you
>> deal with.
>>
> That works, but do you think this could make the things complicated? It
> sounds like different situations have different mechanisms. Why not just
> make the metadata exchanged, any disadvantage for doing that?

Right. Conflict resolution is a layer above syncing. Could be automatic, could
require human intervention (although that's best avoided if possible). Concurrent conflict (e.g. Real-time edit) might/should require human
intervention. But the non-concurrent conflict (e.g. modification caused by
different peers but not at the same time) should be automatically resolved by
the system. Ideally you have a way to go back and undo a change if something important was
lost or overwritten. This is another reason why keeping a versioned metadata
store is good.


--
Sent from Whiteout Mail - https://whiteout.io

My PGP key: https://keys.whiteout.io/mellon@fugue.com

v2.23.0 | Report a Bug | By Email