IETF Logo Mail Archive

Re: [hybi] Payload only compression extension, again

Greg Wilkins <gregw@webtide.com> Wed, 09 March 2011 20:34 UTC

Return-Path: <gregw@intalio.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F73B3A6AB8 for <hybi@core3.amsl.com>; Wed, 9 Mar 2011 12:34:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[AWL=-0.142, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 sCiWMubQs15P for <hybi@core3.amsl.com>; Wed, 9 Mar 2011 12:34:47 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 7E3DD3A6AB5 for <hybi@ietf.org>; Wed, 9 Mar 2011 12:34:47 -0800 (PST)
Received: by vxg33 with SMTP id 33so1039756vxg.31 for <hybi@ietf.org>; Wed, 09 Mar 2011 12:36:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.180.166 with SMTP id dp6mr6597050vdc.63.1299702964080; Wed, 09 Mar 2011 12:36:04 -0800 (PST)
Sender: gregw@intalio.com
Received: by 10.52.169.39 with HTTP; Wed, 9 Mar 2011 12:36:04 -0800 (PST)
In-Reply-To: <AANLkTinCtDepu+wDt4=8GyXqhfn=SQ7v2SjJhKzP2Mzr@mail.gmail.com>
References: <AANLkTik2LqCC2-ZLLdWNNaQ18ypcQU_5djJobkYtYk6T@mail.gmail.com> <AANLkTik+uh98b0n7U=xrE0Aaa7MyBfZVXSwj+8wfVTKW@mail.gmail.com> <AANLkTinCtDepu+wDt4=8GyXqhfn=SQ7v2SjJhKzP2Mzr@mail.gmail.com>
Date: Thu, 10 Mar 2011 07:36:04 +1100
X-Google-Sender-Auth: SEjmLXzCTw3fy5kEzo0FbJOVRVI
Message-ID: <AANLkTinhw0j5U_tvfCCrcEx=J6b7wBua4XzhWkvthUjL@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: Takeshi Yoshino <tyoshino@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: hybi@ietf.org
Subject: Re: [hybi] Payload only compression extension, again
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2011 20:34:48 -0000

On 9 March 2011 23:17, Takeshi Yoshino <tyoshino@google.com> wrote:
> Thanks for feedback.
> On Tue, Mar 1, 2011 at 16:01, Greg Wilkins <gregw@webtide.com> wrote:
>>
>> On 1 March 2011 01:51, Takeshi Yoshino <tyoshino@google.com> wrote:
>> > Hi,
>
>> > - Want not to mess up dictionary by compressing incompressible messages
>>
>> Is that to say that you don't want to compress fragments?
>> I'm cautious about this as we don't want to have to buffer up all
>> fragments before we can decompress.
>>
>
> Sorry, could you elaborate your question?
> I put this in the requirement since IIRC some people said that they want not
> to get some incompressible contents (mixed with compressible contents in a
> single connection) through the compressor. Like this.
> | WS header | BTYPE=01 <compressible contents> | WS header | BTYPE=00
> <incompressible contents> | ...

thanks - that answers my question fine.

cheers

v2.23.0 | Report a Bug | By Email