IETF Logo Mail Archive

Re: Resumable Uploads

Nico Williams <nico@cryptonector.com> Sat, 20 April 2013 05:08 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF25E21F8E6C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 19 Apr 2013 22:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.976
X-Spam-Level:
X-Spam-Status: No, score=-9.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 r2tuuRoflU19 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 19 Apr 2013 22:08:28 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id CDD6821F8E6A for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 19 Apr 2013 22:08:27 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UTQ21-0006uc-RV for ietf-http-wg-dist@listhub.w3.org; Sat, 20 Apr 2013 05:08:13 +0000
Resent-Date: Sat, 20 Apr 2013 05:08:13 +0000
Resent-Message-Id: <E1UTQ21-0006uc-RV@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <nico@cryptonector.com>) id 1UTQ1y-0006rK-GZ for ietf-http-wg@listhub.w3.org; Sat, 20 Apr 2013 05:08:10 +0000
Received: from caiajhbdcbef.dreamhost.com ([208.97.132.145] helo=homiemail-a85.g.dreamhost.com) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <nico@cryptonector.com>) id 1UTQ1x-0004P0-Mm for ietf-http-wg@w3.org; Sat, 20 Apr 2013 05:08:10 +0000
Received: from homiemail-a85.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTP id D84E6BC041 for <ietf-http-wg@w3.org>; Fri, 19 Apr 2013 22:07:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=ZDSa05wW51+b1ElPljsZ Y7mHDT0=; b=s8vkLMSQbjFSLVlu0iEd5NsF2YEmuc9Jwj287SQSOIJk3Mn0TMvN jUUjJXzCIR0NxNxgYMmabAHydqXWId0p+NW9mnsPhlRN1RL2Lxt0lvOYso/dRRh7 xnNkOfobsA7uyhzW922zN21NskSjK/rqTh9BdH8fJL3K129+Z5Bi2f0=
Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTPSA id 8621FBC040 for <ietf-http-wg@w3.org>; Fri, 19 Apr 2013 22:07:48 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id i48so4301140wef.30 for <ietf-http-wg@w3.org>; Fri, 19 Apr 2013 22:07:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=EJ9Ggk0M0yrOVILFKs6g1mICprpQgSlUpCgkpmZhCw8=; b=MvrOwwoedNQCZbhjinBlaBCmV2O6ZP6adMZsTNkFuKb0fLGlTuoBZfmewsb784AsXc UTKV1w313A/bwWQ9oovd1JglseMxzpm89WTrUvL1DcpTfq4f0KG55jjDJq1NYf97xJFK WNPHqDKAodjJOxZssga8XKlTx7Xm8gmGd0mpyWwtt7HxJ5UzrwoiOGUPLpWDy1W2aDMN gzTHYBKq5DY0LVGF5TQCezVnqPEN2j1a79v/uiZn8fciu+YzQfYLw0HKwmb+PHKB3kKC U2ux5zVcaxoCQvmbDCvaL78vB9GHF4WTCLNa77KZNu4/W1mzYeWA3fge2LnZAsi3GNYY lN2g==
MIME-Version: 1.0
X-Received: by 10.194.158.161 with SMTP id wv1mr31736326wjb.38.1366434467194; Fri, 19 Apr 2013 22:07:47 -0700 (PDT)
Received: by 10.216.66.71 with HTTP; Fri, 19 Apr 2013 22:07:47 -0700 (PDT)
Received: by 10.216.66.71 with HTTP; Fri, 19 Apr 2013 22:07:47 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1304192255220.8950@tvnag.unkk.fr>
References: <CADZbJ9dYFGyrceh03M3B0KdKto7160Dis_geh9um0BhVe1re0g@mail.gmail.com> <alpine.DEB.2.00.1304182006001.21288@tvnag.unkk.fr> <29DE6A70-E3B9-4DCE-8C7E-506F6A0ADC92@gmail.com> <51706F32.5030108@panix.com> <5170E2A3.6010706@gmx.de> <CADZbJ9dGEVq-fQmhjRsddYdcg459r_zLfrOddkzHLOprZM0dNg@mail.gmail.com> <51712A49.6000901@gmx.de> <alpine.DEB.2.00.1304191335410.3525@tvnag.unkk.fr> <CABkgnnVFW5zkH-0eY=iyDuFAF9Ua6+4NL26KMP5Nf-cqxmXLJw@mail.gmail.com> <6FD4A73D-08D9-428B-B15A-935691A32BF9@tzi.org> <alpine.DEB.2.00.1304192255220.8950@tvnag.unkk.fr>
Date: Sat, 20 Apr 2013 00:07:47 -0500
Message-ID: <CAK3OfOg=EJtKG41jft-ZpsOz7Grjp15Y2-JZDxL0wbydSByWOw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Daniel Stenberg <daniel@haxx.se>
Cc: Felix Geisendörfer <felix@transloadit.com>, HTTP Working Group <ietf-http-wg@w3.org>, Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="089e013c6ab006addb04dac3d1e6"
Received-SPF: none client-ip=208.97.132.145; envelope-from=nico@cryptonector.com; helo=homiemail-a85.g.dreamhost.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-3.449, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001
X-W3C-Scan-Sig: lisa.w3.org 1UTQ1x-0004P0-Mm 0ec1e988323b10338132b9d4f573b35c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Resumable Uploads
Archived-At: <http://www.w3.org/mid/CAK3OfOg=EJtKG41jft-ZpsOz7Grjp15Y2-JZDxL0wbydSByWOw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17380
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Apr 19, 2013 4:58 PM, "Daniel Stenberg" <daniel@haxx.se> wrote:
>
> On Fri, 19 Apr 2013, Carsten Bormann wrote:
>
>> I'd like to understand the failure model a bit better.
>
>
> I'd just add that a resumed upload does not necessarily imply a previous
upload failure. It could also be that you're appending parts over time as
they "come in" or similar.

Oh, maybe you'd like O_APPEND semantics?  (Not that those are tightly
defined, but you know what I mean.)

Should HTTP have random byte range I/O and byte range locking?  Should it
be a filesystem or object storage protocol?  No, well, maybe; HTTP is every
protocol :)

Nico
--

v2.14.0 | Report a Bug | By Email