Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:97506 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56747 invoked from network); 3 Jan 2017 18:00:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Jan 2017 18:00:08 -0000 X-Host-Fingerprint: 92.66.168.50 unknown Received: from [92.66.168.50] ([92.66.168.50:22815] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 75/7A-55609-4A6EB685 for ; Tue, 03 Jan 2017 13:00:05 -0500 To: internals@lists.php.net Date: Tue, 03 Jan 2017 18:59:59 +0100 Message-ID: References: X-Newsreader: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Posted-By: 92.66.168.50 Subject: Re: [RFC] [VOTE] Add HTTP/2 Server Push Support to ext/curl From: phpdev@ehrhardt.nl (Jan Ehrhardt) Repost, because a message with the real URL was rejected with a reference to why=SURBL on master dot php dot net Hi Davey, Davey Shafik in php.internals (Wed, 9 Dec 2015 13:51:56 -0500): >It's a simple Yes/No 50%+1 majority required as it's not a language change. > > https wiki dot php dot net/rfc/curl_http2_push#vote The RFC was apparently accepted, but the RFC does not tell anything about the implementation. Was it implemented at all? -- Jan