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

Hugo González Labrador <ietf@hugo.labkode.com> Fri, 04 December 2015 20:30 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 E60001A044F for <storagesync@ietfa.amsl.com>; Fri, 4 Dec 2015 12:30:24 -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 j1n-QT8sBNjk for <storagesync@ietfa.amsl.com>; Fri, 4 Dec 2015 12:30:22 -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 6BB181A044E for <storagesync@ietf.org>; Fri, 4 Dec 2015 12:30:22 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id AE67E209CD for <storagesync@ietf.org>; Fri, 4 Dec 2015 15:30:21 -0500 (EST)
Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Fri, 04 Dec 2015 15:30:21 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=labkode.com; h=cc :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=Zix4q/sZWZhX+t+GEpxurbd6Rqs=; b=y3swO6 C53tdYlazbnDQjiejqNwQ2yCJ6SFkL2ZkpS9Gwywr+leANGmrFufCnfh3B3mAZcM aUx11ZP58elX5+2KKv4BGoSBDSqWYrF4L+0xHLDAfwKFqk327ircv3eBiTCRsFSi tClSrIVNipKQMB/pO3HjPft9bK2rWYC+qKWK8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=Zix4q/sZWZhX+t+ GEpxurbd6Rqs=; b=DRkyqPFQ4P2jGvoae/MjJhlLvcjQ9xxVMlwQvQ9CoA1d+n+ QaCCWBjUccMgaSpyjXd83K0K4cMxb4XwZ7tKqGK18RB+pDpdySPxJOFXzW1qRyob ttGlPS+iPouK9VyKZk0LOZ/PWuEXafEnZd6BXC/npEL+i/mkO/IVUP2uHNOc=
Received: by web2.nyi.internal (Postfix, from userid 99) id 6C2D7540117; Fri, 4 Dec 2015 15:30:21 -0500 (EST)
Message-Id: <1449261021.2660424.458369441.7C6FBE34@webmail.messagingengine.com>
X-Sasl-Enc: ET6XMnRv/OZrezDvkX8bMMuxQu+VFInBczqOnkB/RRBG 1449261021
From: Hugo González Labrador <ietf@hugo.labkode.com>
To: Markus Unterwaditzer <markus@unterwaditzer.net>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-5c8c9c89
In-Reply-To: <20151204181850.GB2418@localhost.localdomain>
References: <mailman.108.1449000023.26068.storagesync@ietf.org> <1449004445.2745758.455126129.5028FD2B@webmail.messagingengine.com> <CAO_YprZhCmUxEf=aGCYL=+CLbjUoD1ifpDFsrS7N40Npo4wr+w@mail.gmail.com> <1449050174.3667910.455617161.12EEE3C5@webmail.messagingengine.com> <1449051540970-b577e6c2-393e54ef-bbe05be4@gmail.com> <1449052128.3674794.455635937.667C3E1F@webmail.messagingengine.com> <20151204181850.GB2418@localhost.localdomain>
Date: Fri, 04 Dec 2015 21:30:21 +0100
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/vKVzH11muW8vx38U4CHlqCtL7xo>
Cc: Linhui Sun <lh.sunlinh@gmail.com>, 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: Fri, 04 Dec 2015 20:30:25 -0000


On Fri, Dec 4, 2015, at 07:18 PM, Markus Unterwaditzer wrote:
> On Wed, Dec 02, 2015 at 11:28:48AM +0100, Hugo González Labrador wrote:
> > Of course, the remoteStorage is targeted to browsers, so syncing does
> > not make too much sense in this case. With the rise of Linux container
> > micro-service based architectures, the deployment of  such highly
> > complex systems should become easier and faster.
> 
> It is not exclusively targeted at browsers, although the browser's
> Origin-based
> security model is required for sane client identification. You can
> totally
> access remoteStorage accounts using desktop apps, a proof-of-concept
> exists at
> https://github.com/untitaker/vdirsyncer.
> 

That's great to hear. If this is achievable maybe will be good to
clarify this aspect in the spec.

>From the abstract

    This draft describes a protocol by which client-side applications,
    running inside a web browser, can communicate with a data storage
    server that is hosted on a different domain name. This way, the
    provider of a web application need not also play the role of data
    storage provider. The protocol supports storing, retrieving, and
    removing individual documents, as well as listing the contents of an
    individual folder, and access control is based on bearer tokens.


it is difficult to infer that the spec is also targeted to non-web apps
as there are no mentions to server-side or desktop apps.

As far as I know the OAuth authentication flow works in client-side web
applications, have you managed to use such mechanism in your non-web
project ? That would be a really interesting achievement. Maybe this is
the cause why remoteStorage does not mention non-web apps in their
abstract.


Summoning Michiel to clarify this aspect.

> Synchronisation is a completely unrelated topic. I don't see how it's
> related
> to whether the protocol is targeted at browser applications, in either
> case
> offline sync has to work. And it does.
> 
> I don't understand what you mean with "linux container micro-service
> based
> architectures", or how it is related to this discussion.
> 

That was said to give an example of how using Docker Containers can help
to manage non-monolithic applications. Of course, that is not directly
related to sync.

> -- Markus
> 
> > 
> > Best,
> > 
> > Hugo
> > 
> > > Regards, Linhui
> > >>
> > >>
> > >>> 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
> > >>
> 
> > _______________________________________________
> > Storagesync mailing list
> > Storagesync@ietf.org
> > https://www.ietf.org/mailman/listinfo/storagesync
>