IETF Logo Mail Archive

Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432)

krasic <notifications@github.com> Tue, 12 June 2018 00:09 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E742E130DC6 for <quic-issues@ietfa.amsl.com>; Mon, 11 Jun 2018 17:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ir7YiwyR0gFI for <quic-issues@ietfa.amsl.com>; Mon, 11 Jun 2018 17:09:26 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A17BA12F1AB for <quic-issues@ietf.org>; Mon, 11 Jun 2018 17:09:26 -0700 (PDT)
Date: Mon, 11 Jun 2018 17:09:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528762165; bh=FE7TtFyES2rmx4OFy2BGHhz1jK2UpyiiHgv4/bOE0JI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QyJeSKRtNUJHOLZ2SXFROjEpZ9keXBLaKsk7/A3/VQLQJB23c3lNn+jL11F4/AHd2 w35rmxeTPBeEu8LzYXfs8O69QNm0gtwR/CL5/dCcP6ejwzVCwpwwFH4DZcNjihyy+i ZyWutQIeaWqXyqBsuZsdfPQ56X8PPrE/n0lzaio4=
From: krasic <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc9d1973415a6c95e390e53a53a5eb63335dcf84b92cf000000011736d13592a169ce13b52edd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1432/396424815@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1432@github.com>
References: <quicwg/base-drafts/issues/1432@github.com>
Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f0f35c2dcf_42923f8173406f80167088"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: krasic
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/samV4kCo0aTt9atpW_4mhKxi7GI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2018 00:09:31 -0000

janaiyengar@  if an app isn't to use stream buffers for storage, what does it do in your example when the next consumer isn't keeping up?   if it drains all data from the stream, it may blow up its own memory, unless it implements its own flow control protocol at the app level?   that seems.. unsatisfactory.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1432#issuecomment-396424815

v2.27.8 | Report a Bug | By Email | System Status