Re: [ftpext] COMB command IETF draft proposal

Anthony Bryan <anthonybryan@gmail.com> Thu, 09 June 2011 21:14 UTC

Return-Path: <anthonybryan@gmail.com>
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 5F5F311E810E for <ftpext@ietfa.amsl.com>; Thu, 9 Jun 2011 14:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VQGZm4pVpseL for <ftpext@ietfa.amsl.com>; Thu, 9 Jun 2011 14:14:13 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 89DC111E80FC for <ftpext@ietf.org>; Thu, 9 Jun 2011 14:14:13 -0700 (PDT)
Received: by ywp31 with SMTP id 31so1404607ywp.31 for <ftpext@ietf.org>; Thu, 09 Jun 2011 14:14:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=OxY5UvmSffgtWa9jyjkce4RRkkrP2GYDBw5dM4Ta0n0=; b=XvDuyVW/oTjEmAhF9tvNkCnZ1H+QbdgfGAzkjFt88mWHWhSwGvSfwgV4KKwar8ORTV qSVj59PBEtvNVBpqnHDPVkT+BFOvjgEBh/1QKdPd/vIrUzxMrleDtSokVPVXbsYejACv cP5RzLmXyudL8MY9D/a7uJbgTSaQleG2P+gUg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=vhNbkjXur49CwBvPVVlyEFDc/ITB9tmUJoURyzOnEdGNlluUMasezra6MsWHGnm5Gp Rb9YR3b1Olf+rFxuCKtaGk6MHgjDiiHAvvH3OqorLtVu6EDhSVQeNRQ1AKfFqK8TIQle ZJCr4PO02Mz40FVdfuBCdQM6sk5p/BwkbBSkU=
MIME-Version: 1.0
Received: by 10.91.21.35 with SMTP id y35mr2439596agi.131.1307654052980; Thu, 09 Jun 2011 14:14:12 -0700 (PDT)
Received: by 10.90.73.1 with HTTP; Thu, 9 Jun 2011 14:14:12 -0700 (PDT)
In-Reply-To: <4DF07777.2010205@kimmeringer.de>
References: <F15941D3C8A2D54D92B341C20CACDF2311AC408AB1@exchange> <01AA9EC92749BF4894AC2B3039EA4A2C1946D58A@CH1PRD0302MB131.namprd03.prod.outlook.com> <F15941D3C8A2D54D92B341C20CACDF2311AC51B359@exchange> <BANLkTina+ZF97cgQrJp7yGWcsWmY4eOuEQ@mail.gmail.com> <F15941D3C8A2D54D92B341C20CACDF2311AC51B3C4@exchange> <4DF07777.2010205@kimmeringer.de>
Date: Thu, 09 Jun 2011 17:14:12 -0400
Message-ID: <BANLkTinGVKAQjYmFa+OigDCM3xWBLB0xtQ@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Robert Oslin <rto@globalscape.com>, "ftpext@ietf.org" <ftpext@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [ftpext] COMB command IETF draft proposal
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: Thu, 09 Jun 2011 21:14:14 -0000

On Thu, Jun 9, 2011 at 3:34 AM, Lothar Kimmeringer
<lothar@kimmeringer.de> wrote:
> Am 08.06.2011 22:57, schrieb Robert Oslin:
>>
>> "Have you experienced any issues"
>>
>> - yes, with larger (multi-GB) size files; however there are ways to
>> combine the
>
>> file so that timeouts can be avoided in most cases. I made a couple of
>> fleeting
>> references to those methods in the spec, but really it would be up to the
>> server
>> vendor to research and implement the optimal recombine technique so that
>> timeouts
>> could all but be eliminated for everything but exceedingly large files...
>
> I have to find a way to open docx files so I might repeat something
> that is already supposed but a simple way would be to respond with
> the equivalent of a HTTP-100-response:

it would help to have a text version available.

> C: COMB filea fileb filec
> S: 250-Start COMB
>   250-COMB for filea finished
>   250-COMB for fileb finished
>   250-COMB for filec finished
>   250 COMB command successful
>
> Since a client should in general start over with a timeout every time
> a line of the response has been received, it should help avoid timeouts
> with very large files. In addition to that you receive some feedback,
> that the server is still talking with you.

for HASH we have this:

   Depending on multiple conditions, the final server response to a HASH
   command could take long time, so a server could output a "213-" line
   every 5-10 seconds to avoid the connection being idle and silent.

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads