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

Markus Unterwaditzer <markus@unterwaditzer.net> Mon, 07 December 2015 12:34 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 59F411ACD88 for <storagesync@ietfa.amsl.com>; Mon, 7 Dec 2015 04:34:06 -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 ond01soPmTqQ for <storagesync@ietfa.amsl.com>; Mon, 7 Dec 2015 04:34:05 -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 A362B1ACD86 for <storagesync@ietf.org>; Mon, 7 Dec 2015 04:34:04 -0800 (PST)
Received: (qmail 9076 invoked from network); 7 Dec 2015 12:34:02 -0000
Received: from localhost (HELO localhost) (127.0.0.1) by draco.uberspace.de with SMTP; 7 Dec 2015 12:34:02 -0000
Date: Mon, 07 Dec 2015 13:34:00 +0100
From: Markus Unterwaditzer <markus@unterwaditzer.net>
To: Fei Song <fsong@bjtu.edu.cn>
Message-ID: <20151207123359.GA9854@localhost.localdomain>
References: <2015120710380820341179@bjtu.edu.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <2015120710380820341179@bjtu.edu.cn>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/dNYiUwicXhLSe-hW_8mDwR4uS7g>
Cc: storagesync <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 12:34:06 -0000

Hello Fei, see my response to Lihui Sun.

On Mon, Dec 07, 2015 at 10:38:08AM +0800, Fei Song wrote:
> Hi Markus,
> 
> So, in remoteStorage, what should be stored at the both client and server side?
> Etags or metadata or metadata history or other things?
> based on the draft, it seems that only Etag is enough, but the context in this mailing list confused me...
> 
> 
> 
> 
> Fei Song
> 
> From: Markus Unterwaditzer
> Date: 2015-12-07 05:54
> To: Ted Lemon
> CC: storagesync
> Subject: Re: [Storagesync] Storagesync Digest, Vol 5, Issue 1
> Etags are *much* simpler to implement on the server side than the WebDAV sync
> protocol because they do not require the server to keep sync tokens and
> metadata history. Note that the server has to keep metadata of *deleted* files
> to correctly implement WebDAV's sync protocol. Etags are less efficient in
> terms of network usage of course, but that's the tradeoff to be made.
> 
> I don't know what you mean with the last sentence.
> 
> On Sun, Dec 06, 2015 at 06:26:54PM +0000, Ted Lemon wrote:
> > Sunday, Dec 6, 2015 12:39 PM Markus Unterwaditzer wrote:
> > > What do you mean by "it"? ETags are simpler to implement than the above RFC,
> > > and ETags are also required in WebDAV.
> > 
> > Etags are not really much simpler than a metadata versioning sync protocol, and they are a lot less efficient.   Having to fetch the whole directory for every directory that contains a change is expensive, both for the server and the client, unless changes are infrequent.   And because the server is the sole source of truth, it's a lot more fragile.
> > 
> > 
> > --
> > 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
> 
> 
> 
> 
> _______________________________________________
> Storagesync mailing list
> Storagesync@ietf.org
> https://www.ietf.org/mailman/listinfo/storagesync

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