IETF Logo Mail Archive

Re: [hybi] Framing take IV [why fragment]

John Tamplin <jat@google.com> Thu, 05 August 2010 16:09 UTC

Return-Path: <jat@google.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 95C983A68D0 for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 09:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.856
X-Spam-Level:
X-Spam-Status: No, score=-105.856 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 CArGAPJbe-KY for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 09:09:47 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 2239B3A6823 for <hybi@ietf.org>; Thu, 5 Aug 2010 09:09:42 -0700 (PDT)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12]) by smtp-out.google.com with ESMTP id o75GACna018698 for <hybi@ietf.org>; Thu, 5 Aug 2010 09:10:12 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1281024612; bh=HPR5R2ulZbiJ9cgYzkaL1fR9vF0=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=fgSyAIBP3cNJvuWJcW+zJBysGHq7Jgq1kxtTl5EwHVLdo4rkHU3yH2AoPRs/szBZ9 2xW7KninZETk30q5Kjv5A==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=mcdKMO3mlH8rsY1z6lq/NGBTILOd9e+T0Xhwbl9yzDZDnL4PMtaaQs0sgV//dCHDK uTAfmDEXj+wbPbwANO4WA==
Received: from gxk7 (gxk7.prod.google.com [10.202.11.7]) by hpaq12.eem.corp.google.com with ESMTP id o75G9kMP026641 for <hybi@ietf.org>; Thu, 5 Aug 2010 09:10:10 -0700
Received: by gxk7 with SMTP id 7so2945267gxk.21 for <hybi@ietf.org>; Thu, 05 Aug 2010 09:10:10 -0700 (PDT)
Received: by 10.151.62.16 with SMTP id p16mr12648342ybk.206.1281024610156; Thu, 05 Aug 2010 09:10:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.60.3 with HTTP; Thu, 5 Aug 2010 09:09:50 -0700 (PDT)
In-Reply-To: <2286.1281023493.052316@puncture>
References: <AANLkTinyrDoG5d_Ur6HVRy=SgMPjLzJtpJ++Ye=1DQdj@mail.gmail.com> <Pine.LNX.4.64.1008040050040.5947@ps20323.dreamhostps.com> <1280932393.7561.271.camel@tng> <2286.1281017237.786534@puncture> <AANLkTimWeL5Td0_H0+q+p=CpPqy-GAdhiKxqr5yyGNzL@mail.gmail.com> <2286.1281023493.052316@puncture>
From: John Tamplin <jat@google.com>
Date: Thu, 05 Aug 2010 12:09:50 -0400
Message-ID: <AANLkTimw-YugoJjORDhMrDDx7_EXpT1_Y0qHcQQT+BWz@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary="000e0cd58dded642a6048d15c8c1"
X-System-Of-Record: true
Cc: Server-Initiated HTTP <hybi@ietf.org>
Subject: Re: [hybi] Framing take IV [why fragment]
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: Thu, 05 Aug 2010 16:09:51 -0000

On Thu, Aug 5, 2010 at 11:51 AM, Dave Cridland <dave@cridland.net> wrote:

> Imagine we have frame-based compression (I know this still up for debate,
>> though I think a good case has been made that we need to be able to
>> compress
>> some payloads and not others).
>>
>
> Oh, sure. But that doesn't mean we need to have compression at the frame
> layer.


What would you suggest?  If the entire stream is compressed (which has been
proposed as an alternative to having per-frame compression [which itself
might still share a compression state across frames]), how do you send some
payload frames uncompressed?


> I think the definition of a message is something that an application
> programmer can sensibly write code to react to, so I'd disagree.


If nothing else, updating a progress indicator for downloads of such large
content seems sensible.  It also seems reasonable that media could be
started playing before all of it has been received.

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.23.0 | Report a Bug | By Email