IETF Logo Mail Archive

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

Linhui Sun <lh.sunlinh@gmail.com> Sat, 05 December 2015 05:29 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 0F04A1A0335 for <storagesync@ietfa.amsl.com>; Fri, 4 Dec 2015 21:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] 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 0ZLFkC_KmfWX for <storagesync@ietfa.amsl.com>; Fri, 4 Dec 2015 21:29:08 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 15F941A0302 for <storagesync@ietf.org>; Fri, 4 Dec 2015 21:29:08 -0800 (PST)
Received: by wmuu63 with SMTP id u63so85048164wmu.0 for <storagesync@ietf.org>; Fri, 04 Dec 2015 21:29:06 -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=wzc52UqEpvKbj/jH5GNDYi/qA4oRFCEHsbbnvMa78Q0=; b=RnQdRN3es7+afHr+3RbcdGFkZ/0eRwQQDTvmnU6X4V5iEPAZZU7+42Mp/gojZiHzaW iM8LDh9EhsMPQeabYHk6+TTfqwvU5L8cRTXG1E+mwAIduqmlsFc09TomrZtOMjnMYd/P bKw/nlG0s9NIa8RUiY6R1FWmG7udK3rTf7hTUU0FZxjX2GMqDY3MoKKKN5dkI9o/ok3l ZMtznld5EMhG1rlja4jR15oqIcJg7s5N8VlIcVblfOxFa+OYATFcm43g8NrQ4kCKDOcn 5ubnIVGhiOiTJrGRO1IA66K16plsFyXrrFpCKB6xPziL3ACxpd6uAaCwtsdwEx4ZeeeQ doyA==
X-Received: by 10.194.79.72 with SMTP id h8mr23393018wjx.136.1449293346747; Fri, 04 Dec 2015 21:29:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.27.147 with HTTP; Fri, 4 Dec 2015 21:28:47 -0800 (PST)
In-Reply-To: <1449246571559-58500bfc-f92fedd1-047d217b@fugue.com>
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> <CAPpPfeAdrCZcsYZo7=W6N14K4F2LutXN8BFTetikzKZSr8+vVA@mail.gmail.com> <259424f4.2bca.1516717ef55.Coremail.fsong@bjtu.edu.cn> <56600F0A.9000200@tuxed.net> <CAPpPfeDPHGR+vn0=ji9frF2kr+J=YR76g0e7yOndKzz97bxdHQ@mail.gmail.com> <566014EA.2010705@tuxed.net> <CAO_Yprbc9LMc3TmpkKpmN9hUzAix13nfuSRS5Z8jPf6xu8xjNg@mail.gmail.com> <56601F18.8030409@tuxed.net> <CAO_YpraF1UrV49Po9PZx6ZoSbcLm5gRPEKXAdTT3VvPPPWEAfg@mail.gmail.com> <1449153485919-e58fed74-d7eab50a-01b3670c@fugue.com> <D51EEF1B-13C8-4BBB-91C0-1B473D17759C@cern.ch> <1449170047359-e297ed6e-b9fd94e9-570ca980@fugue.com> <CAO_YpraSokj1S5-mZ17nMiN91c+PfHtMfGSjsFZ1zopQ59eUPQ@mail.gmail.com> <1449246571559-58500bfc-f92fedd1-047d217b@fugue.com>
From: Linhui Sun <lh.sunlinh@gmail.com>
Date: Sat, 05 Dec 2015 13:28:47 +0800
Message-ID: <CAO_YprZOjDN46-kEJhmjbyokRjbPCU2KNK1xrzQiH3vQTm4w9w@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="047d7bb0499e1bbad005261fe740"
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/sseENb70loaek4Szzms7m50DJXY>
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: Sat, 05 Dec 2015 05:29:10 -0000

2015-12-05 0:29 GMT+08:00 Ted Lemon <mellon@fugue.com>:

> Thursday, Dec 3, 2015 10:53 PM Linhui Sun wrote:
> > Separation of metadata and data is better. But I don't understand why we
> > need a distributed peer model. C/S model could still work fine with such
> > separation.
>
> This is correct.   I want the distributed peer model because it's a better
> model, not because the client/server model wouldn't work.
>
I'm not very familiar with the distributed peer model (I view it as p2p,
please correct me if I am wrong). From the example you have provided
previously, it seems that it works fine with 2 participants. But I don't
know whether it works well when multiple participants are willing to share
a file/folder. I'm asking this question since we need to know which model
should the iss probably employ.

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

v2.23.0 | Report a Bug | By Email