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

Linhui Sun <lh.sunlinh@gmail.com> Wed, 02 December 2015 07:20 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 384C11B33E9 for <storagesync@ietfa.amsl.com>; Tue, 1 Dec 2015 23:20:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 Uy7qJ29sspjP for <storagesync@ietfa.amsl.com>; Tue, 1 Dec 2015 23:20:51 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 D15061B33E7 for <storagesync@ietf.org>; Tue, 1 Dec 2015 23:20:50 -0800 (PST)
Received: by wmec201 with SMTP id c201so239238695wme.0 for <storagesync@ietf.org>; Tue, 01 Dec 2015 23:20:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=uGXQrcR70M5wdSDuP9xeqgN/PJCMOhElwBh/XYMPlAw=; b=VCuGZF1M/z8rZZXhLxQ1n8g6oYtforbHZF0zxs6PdEAt/KtktUUQOmJtd0w19PE6+o ph0GOpO9mVVBPos4lc9UMcsiZBrS37z2Q/DwAt/rHekBzE0UXOJD8b+bAQr59TnAYTJO fBO2amAnDHlbItx23pp+nJDhLoFwgu2FR/9NkvcA+/cJDEiEhiMaovJ5ahfLu+KyXUsK I2P21F2BZLEpG/crYJ94j90m+FhnkF5K6Gi6G15LzJaJf77ddSWdWTheBOKnO2/guAtb WHqtFlCoLh1oiiY1iChHgKPjHEc1IA2H+nanw6h4cgWCqXeeRmu0qy5OVbFleYWk+dFV UEyA==
X-Received: by 10.28.89.137 with SMTP id n131mr43621466wmb.9.1449040849464; Tue, 01 Dec 2015 23:20:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.27.147 with HTTP; Tue, 1 Dec 2015 23:20:30 -0800 (PST)
In-Reply-To: <1449004445.2745758.455126129.5028FD2B@webmail.messagingengine.com>
References: <mailman.108.1449000023.26068.storagesync@ietf.org> <1449004445.2745758.455126129.5028FD2B@webmail.messagingengine.com>
From: Linhui Sun <lh.sunlinh@gmail.com>
Date: Wed, 02 Dec 2015 15:20:30 +0800
Message-ID: <CAO_YprZhCmUxEf=aGCYL=+CLbjUoD1ifpDFsrS7N40Npo4wr+w@mail.gmail.com>
To: Hugo González Labrador <ietf@hugo.labkode.com>
Content-Type: multipart/alternative; boundary="001a1140cdb818f1a10525e51d0d"
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/5Aroj48qBmIiha0-CRwTAbBuRNE>
Cc: storagesync <storagesync@ietf.org>, Michiel de Jong <mbdejong@mozilla.com>
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: Wed, 02 Dec 2015 07:20:53 -0000

Hi

2015-12-02 5:14 GMT+08:00 Hugo González Labrador <ietf@hugo.labkode.com>:

> Hi,
>
> from my point of view the remoteStorage project addresses a subset of
> the use cases of the  WebDAV specification.
>
> The main difference I can observe is that the specification is built on
> REST instead of XML-based communication.


> I personally like much more REST than WebDAV because it is more
> developer friendly and it is faster to develop.
>  Maybe the remoteStorage API becomes the next WebDAV :)
>
> However, the remoteStorage API does not provide a way of synchronising
> data, this task is delegated to the developers.
> Is there a plan to provide such feature based on the outcome of this
> draft?
>
I'm a little bit confused why you say the remoteStorage does not provide
that. Is that because remoteStorage does not perform like a typical sync
services (e.g. dropbox...) or you are saying something else?

>
> BTW, I want to introduce ClawIO (http://clawio.github.io), a research
> project to benchmark different synchronisation protocols against
> different data backends with special attention to provide a common sync
> API.
>
> A common API for different sync protocols is being created based on the
> architecture specified in this draft (control and data servers) and the
>
I cannot find a distributed architecture in this draft. It seems that they
handle metadata and content data together, just like a normal web service.

Regards,
Linhui

> one from the CERN EOS project (management, disk and queue servers).
>
> The Phase I has implemented the ownCloud Sync Protocol and Phase II will
> implement the SeaFile Sync Protocol.
> The choice of these protocols among others is because they are really
> opposed to each other in terms of syncing (delta vs non-delta,
> state-based vs log/event/git-based sync …), so finding a common approach
> is more challenging.
>
> Providing a base specification/architecture to measure the feasibility
> of this draft is one of the objectives of the project.
>
> I believe that the work being done here and in ClawIO are supplementary
> to each other and I think mutual collaboration could be beneficial for
> both sides.
>
> Also, if there is interest, the remoteStorage API can be added to
> ClawIO.
>
> Best regards,
>
> Hugo Gonzalez Labrador
>
> On Tue, Dec 1, 2015, at 09:00 PM, storagesync-request@ietf.org wrote:
> > Send Storagesync mailing list submissions to
> >       storagesync@ietf.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >       https://www.ietf.org/mailman/listinfo/storagesync
> > or, via email, send a message with subject or body 'help' to
> >       storagesync-request@ietf.org
> >
> > You can reach the person managing the list at
> >       storagesync-owner@ietf.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Storagesync digest..."
> > Today's Topics:
> >
> >    1. New version of draft-dejong-remotestorage    Internet-Draft
> >       available (Michiel de Jong)
> >    2. Re: New version of draft-dejong-remotestorage Internet-Draft
> >       available (Gihan Dias)
> >    3. Re: New version of draft-dejong-remotestorage Internet-Draft
> >       available (Fei Song)
> > _______________________________________________
> > Storagesync mailing list
> > Storagesync@ietf.org
> > https://www.ietf.org/mailman/listinfo/storagesync
> > Email had 3 attachments:
> > + [Storagesync] New version of draft-dejong-remotestorage
> > Internet-Draft available
> >   2k (message/rfc822)
> > + Re: [Storagesync] New version of draft-dejong-remotestorage
> > Internet-Draft available
> >   1k (message/rfc822)
> > + Re: [Storagesync] New version of draft-dejong-remotestorage
> > Internet-Draft available
> >   2k (message/rfc822)
>
> _______________________________________________
> Storagesync mailing list
> Storagesync@ietf.org
> https://www.ietf.org/mailman/listinfo/storagesync
>