Re: [core] Disentangle Block and Token
Klaus Hartke <hartke@tzi.org> Mon, 16 April 2012 22:14 UTC
Return-Path: <hartke@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BFE511E80C1 for <core@ietfa.amsl.com>; Mon, 16 Apr 2012 15:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level:
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eolc6PYnlBHV for <core@ietfa.amsl.com>; Mon, 16 Apr 2012 15:14:11 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id AB87311E80B6 for <core@ietf.org>; Mon, 16 Apr 2012 15:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q3GME2CG000360 for <core@ietf.org>; Tue, 17 Apr 2012 00:14:02 +0200 (CEST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 8B4B0989 for <core@ietf.org>; Tue, 17 Apr 2012 00:14:02 +0200 (CEST)
Received: by pbbrp16 with SMTP id rp16so4812312pbb.31 for <core@ietf.org>; Mon, 16 Apr 2012 15:14:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.135.226 with SMTP id pv2mr30936189pbb.148.1334614440468; Mon, 16 Apr 2012 15:14:00 -0700 (PDT)
Received: by 10.68.23.37 with HTTP; Mon, 16 Apr 2012 15:14:00 -0700 (PDT)
Date: Tue, 17 Apr 2012 00:14:00 +0200
Message-ID: <CAB6izETgm3-Xchm+UQDd3Koxqy0iag5k84MsCi7o2AUJQryDzQ@mail.gmail.com>
From: Klaus Hartke <hartke@tzi.org>
To: core@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [core] Disentangle Block and Token
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 22:14:11 -0000
On 16 April 2012 11:01, core issue tracker <trac+core@trac.tools.ietf.org> wrote: > 3. similarly, for the state for atomic POST/PUT ("context"): > select this per end-point (and URI), too. > > * note that this means a new upload to the same URI (before an old > one from the same endpoint was finished) simply overwrites the > context. This is probably exactly what one wants. Who wins if two clients perform a block-wise atomic POST/PUT with the same URI through the same proxy at the same time? Klaus
- Re: [core] Disentangle Block and Token Klaus Hartke
- Re: [core] Disentangle Block and Token Carsten Bormann
- Re: [core] Disentangle Block and Token Klaus Hartke