IETF Logo Mail Archive

Re: [ftpext] New Version of FTP HASH, RANG, LOCK, and HOST

Hans Andersen <hans@enterprisedt.com> Sat, 02 February 2013 05:59 UTC

Return-Path: <hans@enterprisedt.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 CDB1721F8E0A for <ftpext@ietfa.amsl.com>; Fri, 1 Feb 2013 21:59:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.642
X-Spam-Level:
X-Spam-Status: No, score=-1.642 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
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 BLcSC1O+2Tvs for <ftpext@ietfa.amsl.com>; Fri, 1 Feb 2013 21:59:37 -0800 (PST)
Received: from enterprisedt.com (mail.enterprisedt.com [67.225.246.158]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB0921F8E03 for <ftpext@ietf.org>; Fri, 1 Feb 2013 21:59:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=enterprisedt.com; s=default; h=Content-Type:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=GhEHCVDmpVuH7P4J1PFyiOWJCDRrzqAuMRn5xC8/RUU=; b=DXvKUBI72yFR7G7Hl085uqPAYiChdNcavTXPwULCRcDdXktAKlIDC2AYy+TPs31YEDciNNJ/2cWmTV7AjijKQ4iKsqr2WwMdFP+xkqSBpJjw2eoy1ihMShLWqGJ1jOdj;
Received: from mail-ia0-f173.google.com ([209.85.210.173]:46590) by host.enterprisedt.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80) (envelope-from <hans@enterprisedt.com>) id 1U1W8W-0007rm-KL for ftpext@ietf.org; Sat, 02 Feb 2013 15:59:36 +1000
Received: by mail-ia0-f173.google.com with SMTP id h37so1934814iak.4 for <ftpext@ietf.org>; Fri, 01 Feb 2013 21:59:35 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.151.176 with SMTP id ur16mr791443igb.30.1359784775932; Fri, 01 Feb 2013 21:59:35 -0800 (PST)
Received: by 10.64.137.39 with HTTP; Fri, 1 Feb 2013 21:59:35 -0800 (PST)
In-Reply-To: <CANqTPehG4erM8k622DV8Ou6DLGkpfM92RewUVA69KwA6hetxQg@mail.gmail.com>
References: <CANqTPegPaMBF9i1gi+M3m5FXzuxRzUU_QULxB_sdJTVd7NGppQ@mail.gmail.com> <51009243.4080809@gmail.com> <51056391.2070901@gmail.com> <03ec01cdfcbc$b247bef0$16d73cd0$@texis.com> <5105BDA8.7000006@gmail.com> <CANqTPehG4erM8k622DV8Ou6DLGkpfM92RewUVA69KwA6hetxQg@mail.gmail.com>
Date: Sat, 02 Feb 2013 15:59:35 +1000
Message-ID: <CAATrTKZN_d1e4gGzpQbcNQnz028Eg7zgTvZ=bv5+y1uULsh5_Q@mail.gmail.com>
From: Hans Andersen <hans@enterprisedt.com>
To: "ftpext@ietf.org" <ftpext@ietf.org>
Content-Type: multipart/alternative; boundary="e89a8f3b9f3b8a5b9e04d4b79040"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.enterprisedt.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - enterprisedt.com
Subject: Re: [ftpext] New Version of FTP HASH, RANG, LOCK, and HOST
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, 02 Feb 2013 05:59:37 -0000

I just wanted to back my colleague, Bruce, on the performance issue related
to detecting boundaries.  A few weeks ago I wrote code that detects MIME
boundaries in HTTP-POSTs while piping the data to a file.  The best I
managed to achieve was significantly slower than simple piping.  I
therefore think that optionally including the size is important for
performance.

On 2 February 2013 14:26, Anthony Bryan <anthonybryan@gmail.com> wrote:

> right, we could leave the boundary REQUIRED but have an OPTIONAL size
> that would be used (probably the majority of the time?)

v2.23.0 | Report a Bug | By Email