Re: [quicwg/base-drafts] http deadlock with stream FIN choices (#1972)
Dmitri Tikhonov <notifications@github.com> Thu, 15 November 2018 02:50 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 72629130DDC for <quic-issues@ietfa.amsl.com>; Wed, 14 Nov 2018 18:50:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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] 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 ZpFROpqUfENK for <quic-issues@ietfa.amsl.com>; Wed, 14 Nov 2018 18:50:46 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4448012777C for <quic-issues@ietf.org>; Wed, 14 Nov 2018 18:50:46 -0800 (PST)
Date: Wed, 14 Nov 2018 18:50:44 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542250244; bh=nA3Uy+JAk1tdPVFNiyfTQxl0Y5dAHbDr0gA/kk5C7b0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fZenEmTz8rJtbaiZlndbLcBzccuS+K9Gla5VZurU9DsXbeG7YJ8xJvMZNe2+6bidr JK0o5ImAP+JppMCGVKXJbMAPycCrcqqwxHdWNaUAGs8w4HUneo3wMuv0T/b3eDDvtc ngZWFmqhZ8YmH2al9GyJexwwiNt7VFepTRHuLK1I=
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2cafb34627e67c3254b9028303660fc909e705c492cf000000011804a10492a169ce1683c825@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1972/438897761@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1972@github.com>
References: <quicwg/base-drafts/issues/1972@github.com>
Subject: Re: [quicwg/base-drafts] http deadlock with stream FIN choices (#1972)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5becdf04e9434_311b3fbf9ced45b8464c7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dtikhonov
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/gjgjwJm4n8NMaCXPJS2_U-k3g1U>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 15 Nov 2018 02:50:51 -0000
> [...] I have a problem with the implication that you can wait for the entire message to arrive before you begin processing it. _That's_ the original incompatible bug that started this issue. Is it? The first sentence in this thread reads: > During interop, I couldn't interop with winquic because I never FIN my request stream, and winquic doesn't serve the response until the request FINs. Plus, it really depends on the type of the request? For example, if one is to calculate MD5 sum of the request body and return it as response body (something we did during last interop), one must wait for FIN. An echo-type service (another interop example) must process request body immediately (echo it back) and does not have to wait for FIN. -- 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/1972#issuecomment-438897761
- Re: [quicwg/base-drafts] http deadlock with strea… martinduke
- [quicwg/base-drafts] http deadlock with stream FI… martinduke
- Re: [quicwg/base-drafts] http deadlock with strea… Nick Banks
- Re: [quicwg/base-drafts] http deadlock with strea… afrind
- Re: [quicwg/base-drafts] http deadlock with strea… Kazuho Oku
- Re: [quicwg/base-drafts] http deadlock with strea… Ryan Hamilton
- Re: [quicwg/base-drafts] http deadlock with strea… Lucas Pardue
- Re: [quicwg/base-drafts] http deadlock with strea… Nick Banks
- Re: [quicwg/base-drafts] http deadlock with strea… Lucas Pardue
- Re: [quicwg/base-drafts] http deadlock with strea… MikkelFJ
- Re: [quicwg/base-drafts] http deadlock with strea… Nick Banks
- Re: [quicwg/base-drafts] http deadlock with strea… Kazuho Oku
- Re: [quicwg/base-drafts] http deadlock with strea… Mike Bishop
- Re: [quicwg/base-drafts] http deadlock with strea… martinduke
- Re: [quicwg/base-drafts] http deadlock with strea… Mike Bishop
- Re: [quicwg/base-drafts] http deadlock with strea… Dmitri Tikhonov
- Re: [quicwg/base-drafts] http deadlock with strea… David Schinazi
- Re: [quicwg/base-drafts] http deadlock with strea… Kazuho Oku
- Re: [quicwg/base-drafts] http deadlock with strea… David Schinazi
- Re: [quicwg/base-drafts] http deadlock with strea… Ryan Hamilton
- Re: [quicwg/base-drafts] http deadlock with strea… Mike Bishop
- Re: [quicwg/base-drafts] http deadlock with strea… Dmitri Tikhonov
- Re: [quicwg/base-drafts] http deadlock with strea… Ryan Hamilton
- Re: [quicwg/base-drafts] http deadlock with strea… Mike Bishop