Re: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-hash-00.txt

Sob <sob@nvnet.cz> Sat, 07 April 2012 02:34 UTC

Return-Path: <sob@nvnet.cz>
X-Original-To: ftpext@ietfa.amsl.com
Delivered-To: ftpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 527E521F857D for <ftpext@ietfa.amsl.com>; Fri, 6 Apr 2012 19:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Level:
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_CZ=0.445, RDNS_NONE=0.1]
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 QTXcelcERqJR for <ftpext@ietfa.amsl.com>; Fri, 6 Apr 2012 19:34:34 -0700 (PDT)
Received: from mail.nvnet.cz (mail.nvnet.cz [IPv6:2002:d5d3:2ff6:80::3]) by ietfa.amsl.com (Postfix) with ESMTP id 05B5421F8559 for <ftpext@ietf.org>; Fri, 6 Apr 2012 19:34:33 -0700 (PDT)
X-AuthUser: sob@nvnet.cz
Received: from Sob-PC.nvnet.cz ([213.211.47.246]:60807) by mail.nvnet.cz with [XMail 1.25 ESMTP Server] id <S2BEC> for <ftpext@ietf.org> from <sob@nvnet.cz>; Sat, 7 Apr 2012 04:34:04 +0200
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sat, 07 Apr 2012 04:32:47 +0200
To: Mat Berchtold <mb@smartftp.com>,Anthony Bryan <anthonybryan@gmail.com>
From: Sob <sob@nvnet.cz>
In-Reply-To: <36F3A30DD743D74C9BE4FF935AB5B5F30E2599A5@m.smartsoft.local >
References: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> <CANqTPejDknRFSGg_0Gm_24GKbiZ9-yfMBW2A9kTibAcdeh97Ag@mail.gmail.com> <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local> <CANqTPeh_FJNCT5gpnNyVTEQQKt8FUxUaDxmKJv6CHcFQb+yfUA@mail.gmail.com> <36F3A30DD743D74C9BE4FF935AB5B5F30E2599A5@m.smartsoft.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20120407023434.05B5421F8559@ietfa.amsl.com>
Cc: "ftpext@ietf.org" <ftpext@ietf.org>
Subject: Re: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-hash-00.txt
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sat, 07 Apr 2012 02:34:35 -0000

At 03:10 7.4.2012, Mat Berchtold wrote:
>The range can be passed directly to the command as optional arguments:
>hash-command = "HASH" SP pathname [ SP start-point [ SP end-point ] ]

It can't, at least not like this, simply because if the server gets, e.g.:

HASH somepath 10 20

.. it can mean any of the following and it's impossible to tell which one:

a) pathname = "somepath", start-point = 10, end-point = 20
b) pathname = "somepath 10", start-point = 20
c) pathname = "somepath 10 20"

It would work with reversed order, with mandatory start and end 
points before pathname, but if RANG catches up (and it should, 
because it has big potential), wouldn't it be a little weird to have 
separate way for using ranges with HASH?

--