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

Hugo González Labrador <ietf@hugo.labkode.com> Fri, 04 December 2015 21:28 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 4A9C71A90C9 for <storagesync@ietfa.amsl.com>; Fri, 4 Dec 2015 13:28:37 -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 G2KwfWOeptvm for <storagesync@ietfa.amsl.com>; Fri, 4 Dec 2015 13:28:33 -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 46A201A90C0 for <storagesync@ietf.org>; Fri, 4 Dec 2015 13:28:33 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 78A232051E for <storagesync@ietf.org>; Fri, 4 Dec 2015 16:28:32 -0500 (EST)
Received: from web2 ([10.202.2.212]) by compute4.internal (MEProxy); Fri, 04 Dec 2015 16:28:32 -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=9ieMlPyvDpLqAJDHv4oVbZQVin0=; b=APN/of XIgWN85+WDrgr65ZgrQ+++3mIgZgs93mP7lz27U9WgoOR6/06bpt+1UcqRrYUQ5b 399NBzTWnMtcRUKMX/SNSTW/whZUgDjgz52p3JV1Iczwwmy8mAYd/sYwWrnXyATj 1uZ+c/VTeSiuiOmAmTsuzm/ZM6IJxyDLu2ZNo=
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=9ieMlPyvDpLqAJD Hv4oVbZQVin0=; b=TmFPn7Y1QQTr/YycMAybHV+Qv0je8wXl8IZ5D6wSAa4QKK0 Vsx5xZ5Pv7zDS3BiAtro1ZCkC0IZya5V74fmKxLdW9h9ChqSNqLWYiHhj2vgXTiH vDK4mcaXskuMj3gddW6f8MZbhY67CdJmwtBEvml34JjILIAjWdm78e2IZVcM=
Received: by web2.nyi.internal (Postfix, from userid 99) id 27EF3540141; Fri, 4 Dec 2015 16:28:32 -0500 (EST)
Message-Id: <1449264512.2853440.458418905.051FE0CD@webmail.messagingengine.com>
X-Sasl-Enc: 4dAEvGqVCRygVq+mNGxPEBFkaKWFj3F1j7WJQrmLBjrI 1449264512
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
Date: Fri, 04 Dec 2015 22:28:32 +0100
In-Reply-To: <20151204211411.GA9979@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> <1449261021.2660424.458369441.7C6FBE34@webmail.messagingengine.com> <20151204211411.GA9979@localhost.localdomain>
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/g1eSgmCOJNO1HTr9gjhIqWLLFDE>
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 21:28:37 -0000


On Fri, Dec 4, 2015, at 10:14 PM, Markus Unterwaditzer wrote:
> > 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.
> 
> (Apologies to skippe and others who've had this discussion with me
> already)
> 
> I'll have to back-paddle a bit.
> 
> Yes, it's possible. It is possible AND secure if the server requires
> stricter
> methods for app identification, which is stated in the spec as a MAY. The
> spec
> does focus on web applications, and they're the supported usecase.
> 
> The way I've made my particular desktop application work is sort-of a
> hack, but
> may be less fragile if the application has full control over the browser
> window
> (e.g. WebView on Android, or bundled webkit browser for desktop apps)
> 

Okay, I see. So, web applications are the supported use case by
remoteStorage but there are alternatives, as you have explained, that
make it possible to connect from non web apps using embedded browsers. 

I would like to hear Michiel opinion on this subject to see if
remoteStorage will have non web apps as a supported use case in the
future or if it is out of scope.

Best,

Hugo

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