Re: Multi-GET, extreme compression?

Nico Williams <nico@cryptonector.com> Tue, 19 February 2013 07:00 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5E2821F8D64 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 18 Feb 2013 23:00:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.803
X-Spam-Level:
X-Spam-Status: No, score=-7.803 tagged_above=-999 required=5 tests=[AWL=2.174, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_HI=-8]
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 9G0HHr9o88Th for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 18 Feb 2013 23:00:37 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id BB3DE21F8D02 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 18 Feb 2013 23:00:36 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1U7hBG-0006Yk-As for ietf-http-wg-dist@listhub.w3.org; Tue, 19 Feb 2013 06:59:58 +0000
Resent-Date: Tue, 19 Feb 2013 06:59:58 +0000
Resent-Message-Id: <E1U7hBG-0006Yk-As@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <nico@cryptonector.com>) id 1U7hB8-0006XT-GU for ietf-http-wg@listhub.w3.org; Tue, 19 Feb 2013 06:59:50 +0000
Received: from caiajhbdcagg.dreamhost.com ([208.97.132.66] helo=homiemail-a24.g.dreamhost.com) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <nico@cryptonector.com>) id 1U7hB7-0000FN-JM for ietf-http-wg@w3.org; Tue, 19 Feb 2013 06:59:50 +0000
Received: from homiemail-a24.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTP id C6DFA2C806C for <ietf-http-wg@w3.org>; Mon, 18 Feb 2013 22:59:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=2Qg1WX+J80P51YrPG3px xznbQEQ=; b=mcgW9FYKtrV8gyoOEkp8X8YUFghJAR9PVG8WQB0QqdhcWuvw7EKg mjb3oarxhZrG9mbaXB4VnEE7F30evcOaFtSZyxogor1qpVe2Qu07Al1pQvF7eIhW D/pAArwCUUvQOGLRVWE7CznZd9DLFnTv8NIKmovEgycjFWMmYlYS20k=
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTPSA id 7079A2C806B for <ietf-http-wg@w3.org>; Mon, 18 Feb 2013 22:59:27 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id o1so4404152wic.5 for <ietf-http-wg@w3.org>; Mon, 18 Feb 2013 22:59:26 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.180.91.106 with SMTP id cd10mr5996965wib.6.1361257161012; Mon, 18 Feb 2013 22:59:21 -0800 (PST)
Received: by 10.216.254.217 with HTTP; Mon, 18 Feb 2013 22:59:20 -0800 (PST)
In-Reply-To: <46B6BA9A-E9ED-4BD1-8675-62FEA627B688@mnot.net>
References: <CAMm+LwiF6EM8_aQgUm=nPS5XqaG25iRGNke_rnHTM1vTGMXdfg@mail.gmail.com> <CAK3OfOhBe8UdzqvNaA+pb+e=TZytsQQfp1S8pH2N_3GUk2mUgw@mail.gmail.com> <E2C47AB2-03C6-48B7-A345-C896F44D7B86@mnot.net> <CAK3OfOh0sLJBGdWpUqX6FAe40=FyKRWPyqMmMyAQF_Uy=94Z=g@mail.gmail.com> <46B6BA9A-E9ED-4BD1-8675-62FEA627B688@mnot.net>
Date: Tue, 19 Feb 2013 00:59:20 -0600
Message-ID: <CAK3OfOiH7Q3TEkNLbwN=FaO4vnEGX22hsquyO2CtE4L+PXn3eQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Phillip Hallam-Baker <hallam@gmail.com>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: none client-ip=208.97.132.66; envelope-from=nico@cryptonector.com; helo=homiemail-a24.g.dreamhost.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-3.361, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001
X-W3C-Scan-Sig: maggie.w3.org 1U7hB7-0000FN-JM 6cdd6a7d64b40e4772e19ccedb849326
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Multi-GET, extreme compression?
Archived-At: <http://www.w3.org/mid/CAK3OfOiH7Q3TEkNLbwN=FaO4vnEGX22hsquyO2CtE4L+PXn3eQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16682
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Mon, Feb 18, 2013 at 11:07 PM, Mark Nottingham <mnot@mnot.net> wrote:
> On 19/02/2013, at 3:44 PM, Nico Williams <nico@cryptonector.com> wrote:
>> Is Phillip's proposal also out of charter?
>
> If it requires significant modification of HTTP APIs to function, or changes to HTML, yes.

I think neither.  Think of a header by which I ask for a tarball (or
whatever suitable archive format) with the resource and related
sub-resources?  How would such an extension require changes to HTTP
APIs or HTML?  I think it's neither.  It would require changes to the
server, but if the server doesn't grok this header no problem ensues:
the client can tell what happened because of the content type of the
result (assuming success).  To be fair the obvious way to code this on
the client would be either as a wrapper to HTTP APIs (I assume you
meant APIs to HTTP, as opposed to APIs accessed via HTTP) or as
extensions to HTTP APIs.

(And if you really meant HTTP APIs as in APIs accessed via HTTP then I
think those also would require no changes.)

>>> Again, if you have a proposal, please write it up in detail and make it to the WG; endlessly discussing the minutia of a half-formed idea is not a productive use of anyone's time.
>>
>> I... posted twice on this, within minutes.
>
> Yes, but it's not about a simple post count. It's about continuing a thread where I'd already suggested making a more well-formed proposal before continuing discussion.

Ah, my sin then was not reading the whole thread first.  Sorry.

Nico
--