Re: [quicwg/base-drafts] [feature] Push messaging from server to client (#2664)

Patrick <> Wed, 01 May 2019 17:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7D15D1200FE for <>; Wed, 1 May 2019 10:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id j7Qox6GbFCIK for <>; Wed, 1 May 2019 10:41:37 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8A8951200B6 for <>; Wed, 1 May 2019 10:41:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=TH6VFcOd9aRUt/C+HpEcYVzwNhU=; b=M1pXpvCA447o1hco WEkYN/G+CXvyB1L3T9rwxfLrAnJEyvqLqU9h6jG45JnnF49jaJYyEFDj6UAAlMI8 YoERjj78zodMetTR5FUODPQBsgUyAz8WAn1Aw+QRwVrImDvaF+U/4QZCLPMsvUku HZ5iEWuKzpMaunFZQorNg6gTwcc=
Received: by with SMTP id filter1093p1las1-20616-5CC9DA4F-3C 2019-05-01 17:41:35.710285378 +0000 UTC m=+503879.055329223
Received: from (unknown []) by (SG) with ESMTP id 1jsiYhb4Q-mZ7ZqL3dJoaA for <>; Wed, 01 May 2019 17:41:35.616 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 85ABEC0B64 for <>; Wed, 1 May 2019 10:41:35 -0700 (PDT)
Date: Wed, 01 May 2019 17:41:35 +0000 (UTC)
From: Patrick <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2664/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] [feature] Push messaging from server to client (#2664)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cc9da4f843cd_17103f8ca3ccd96c5327fd"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: wzr1337
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0Wy01F5JYaMtVc6AmKIX7/YI/87Y25t1/wrE R2e/Crt/5n+u/9oqhKsS3cWO93LnPcSttjXbMepHlktdX+HKdSK8b3t3fAGb93PjStvqE5jvDy0QkB eXpni2/uJfFY/NJPfchuZKLvCdypBYeh0mrV7MPoaP06nENLLSGR/8A7dQ==
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 01 May 2019 17:41:41 -0000

well there are a couple of solutions possible. As described in the spec I reference to, WebSockets are used, replicating some of the HTTP headers and a topic. 

With this proposal, I want to reduce friction. Why setup two sockets, if you can handle it via one?

The socket you use for HTTP GET, PUT, POST etc. would have to kept open but could then be used to push information in the other direction.

Think of a multi-repsonse GET request. Super convenient to work with from developers point of view on both ends of the connection. No extra protocol needed, no extra syntax to learn. Just multiple responses to the same GET request, either on an `on change` or a periodic basis, limited to a certain rate by either the client or the server.

**Use-case 1 - chat messages**
SUB /messages/

initial response
290 OK

1st data response
200 OK

2nd data response (100ms later)
200 OK


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: