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

Hugo González Labrador <ietf@hugo.labkode.com> Tue, 01 December 2015 21:14 UTC

Return-Path: <ietf@hugo.labkode.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 790001B3B10 for <storagesync@ietfa.amsl.com>; Tue, 1 Dec 2015 13:14:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_8BIT_HEADER=0.3, 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 Xdr6kXfethYo for <storagesync@ietfa.amsl.com>; Tue, 1 Dec 2015 13:14:06 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 458AB1B3B0A for <storagesync@ietf.org>; Tue, 1 Dec 2015 13:14:06 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 9CA09202D0 for <storagesync@ietf.org>; Tue, 1 Dec 2015 16:14:05 -0500 (EST)
Received: from web2 ([10.202.2.212]) by compute3.internal (MEProxy); Tue, 01 Dec 2015 16:14:05 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=labkode.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=JPqBXmOP5LPJS1fFFbQuSnuS5lU=; b=o4QwRD irxh1ycmsV+JnxcYZs2ZF8h15d8u7iQ9X5qaDsnH0gbikyuxQKJT0yUAesfIVtnT yGIzWqGn/f94sT3ugfgOnqU79a3pXaV7znvB+ZBoi+L1xsWsi95fcDMh3FVDX/wk AYac/jWaNZdvO4vVQz24aqohDk9iqdFk4fTto=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=JPqBXmOP5LPJS1f FFbQuSnuS5lU=; b=Af06ZU3VNj+RQngNs1MFVh6eloIvuOM27uqqiabokM2lkOW YHKLZkIkmhdSIlz9/LvmpNNtmp4tQxlEM/EbihG1QF75SPMmjVJDWL6WQPAiJ/iZ cdmf4ufFAWaH0Wpc7afV+BVjTIA0KBNxQT8wJdU2/y80aO3aHBIU4Fq3RuUE=
Received: by web2.nyi.internal (Postfix, from userid 99) id 6C5CC5401FE; Tue, 1 Dec 2015 16:14:05 -0500 (EST)
Message-Id: <1449004445.2745758.455126129.5028FD2B@webmail.messagingengine.com>
X-Sasl-Enc: tTqB/4YQ+BhnlvxSDQOz2qdMfZHWU5OI7T3CyZ3WXvzw 1449004445
From: Hugo González Labrador <ietf@hugo.labkode.com>
To: storagesync@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-b94e6169
In-Reply-To: <mailman.108.1449000023.26068.storagesync@ietf.org>
References: <mailman.108.1449000023.26068.storagesync@ietf.org>
Date: Tue, 01 Dec 2015 22:14:05 +0100
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/Th5ljvWidpiUDcR6wyZYIVYBy0E>
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, 01 Dec 2015 21:14:08 -0000

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?

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
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)