Re: [ftpext] End byte of transfer in FTP
Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com> Sun, 05 December 2010 09:25 UTC
Return-Path: <tatsuhiro.t@gmail.com>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A5D13A6A55 for <ftpext@core3.amsl.com>; Sun, 5 Dec 2010 01:25:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level:
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T+tZUanlZn+m for <ftpext@core3.amsl.com>; Sun, 5 Dec 2010 01:25:46 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 2456E3A69B9 for <ftpext@ietf.org>; Sun, 5 Dec 2010 01:25:45 -0800 (PST)
Received: by fxm9 with SMTP id 9so9255044fxm.31 for <ftpext@ietf.org>; Sun, 05 Dec 2010 01:27:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=ztCnUb22vg3re8AdVogJyKvk+B+J9BAd/Iyu6u2TB1k=; b=Vx2czZevzA8IeC6lEvPCl9aato4+G17BvyHUs/7sQy6bxfbUp7gqA5eSLwi1UfDIcx lxMgNfd1V/mL7XhS36+UboxErSxnXVdhGV/H3ZNQUnwKqjhRm3vlzG4BOTvmuDP41KC6 n0wfI8GdPyDhYT73KL/U4eivkcsy73eRwdKx0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=rYRqgT7Yn0T/DLJpC6xXn3Iy5UX4PJGLrdmJvQtPZCgcDfgTxzunfY2PtVgPzcka3i 32mK876ecBucYBhE2QskdCX9xffGlbkM5zEgZo4hE2z1OEHXx9az0xnjVSqCoHf06vup kgdeJXoSxO1LahqlBloLMcrzW8t0V7svYSlrM=
Received: by 10.223.36.220 with SMTP id u28mr3364053fad.11.1291541226684; Sun, 05 Dec 2010 01:27:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.83.200 with HTTP; Sun, 5 Dec 2010 01:26:46 -0800 (PST)
In-Reply-To: <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr> <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com>
From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Sun, 05 Dec 2010 18:26:46 +0900
Message-ID: <AANLkTiks7Yx9C3kEzJSHr=0oHjBrg4RhBkFAwZBQn8p7@mail.gmail.com>
To: Anthony Bryan <anthonybryan@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org, Daniel Stenberg <daniel@haxx.se>
Subject: Re: [ftpext] End byte of transfer in FTP
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Dec 2010 09:25:47 -0000
2010/12/5 Anthony Bryan <anthonybryan@gmail.com>: > > would it be possible to modify REST so that if the FEAT reply included RANGE: > > C> feat > S> 211- <any descriptive text> > S> ... > S> REST STREAM RANGE > S> ... > S> 211 end > > REST could take a starting point and ending point? > I don't know it is possible to extend existing command to get another argument. But if it can, it is reasonable. If it cannot, then we can make another command, say, RANG(or RNGE?) which takes starting and ending point. > if so, I wonder if servers & clients would want to implement that or > if it's too late in the game. > At least for client, I'd love to implement this extension in aria2;) I think it is not too late, because there is big difference with or without standard. And still FTP is widely used and FTP server code is maintained, so there is a plenty of room for this extension. Best regards, Tatsuhiro Tsujikawa
- [ftpext] End byte of transfer in FTP Tatsuhiro Tsujikawa
- Re: [ftpext] End byte of transfer in FTP John C Klensin
- Re: [ftpext] End byte of transfer in FTP Richard Koenning
- Re: [ftpext] End byte of transfer in FTP Tatsuhiro Tsujikawa
- Re: [ftpext] End byte of transfer in FTP Daniel Stenberg
- Re: [ftpext] End byte of transfer in FTP Tatsuhiro Tsujikawa
- Re: [ftpext] End byte of transfer in FTP Anthony Bryan
- Re: [ftpext] End byte of transfer in FTP Tatsuhiro Tsujikawa
- Re: [ftpext] End byte of transfer in FTP Daniel Stenberg
- Re: [ftpext] End byte of transfer in FTP John C Klensin
- Re: [ftpext] End byte of transfer in FTP Richard Koenning
- Re: [ftpext] End byte of transfer in FTP Tatsuhiro Tsujikawa