Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90722 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26443 invoked from network); 19 Jan 2016 23:24:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Jan 2016 23:24:47 -0000 Authentication-Results: pb1.pair.com smtp.mail=me@daveyshafik.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=me@daveyshafik.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain daveyshafik.com from 209.85.192.41 cause and error) X-PHP-List-Original-Sender: me@daveyshafik.com X-Host-Fingerprint: 209.85.192.41 mail-qg0-f41.google.com Received: from [209.85.192.41] ([209.85.192.41:36687] helo=mail-qg0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B6/70-22584-DB5CE965 for ; Tue, 19 Jan 2016 18:24:47 -0500 Received: by mail-qg0-f41.google.com with SMTP id e32so505540203qgf.3 for ; Tue, 19 Jan 2016 15:24:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=daveyshafik-com.20150623.gappssmtp.com; s=20150623; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZFZsVk6lmq9xqOdGHklUsvhJOkWpU/QwS8CU/HpKfxw=; b=EbhgULTrFMUTHB5xtQe//dWxKAxb3sasKInSOyayyvB81Z/yLOI/wO+l/njqmH+WGF esstIIM/lVWQuqqOkDF8T3n6qVISwT7dP7Od6N6+t7OPzTi4Vp2MvnIzhItJnOUq+gdD AwmHFdcq+QFrlK+7mRGOsVxUHJLF4jT8azF2aNGEumrEiSlV+pAyvSM92utoG1q66i4T 50a4pJfCWHQoYKCtlw1JjPY3Z0vxexjtxDu/xfxGlHymkF/krCvwpHzusCiMQNQsztz5 /+vespFoqWmiUOEfUdYWz8Px/DDQZePTNdIt0JoahCtWGriIdSGTAHgZsiqAKuqj1UW+ z5hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=ZFZsVk6lmq9xqOdGHklUsvhJOkWpU/QwS8CU/HpKfxw=; b=OPEVqFitD+8hMjlODHrGkRCGCLilOcTBpHHd2dWRIeuwGRWECPp1jOImUwiWxaxryu dmLu1Bpn0Y2dlDRjekeE97KUT5ugyCi1vt4JBKNiSNu9dqYofSxPyniZUmucYm9Op393 XHkTVhyIelqDntKmzsBkIL2lf56iEspFotjqd8xD6Tdnj/f0KqDB5mSEyxorpDLlBm4V 7+ASoYyzi+JzdHik2h+gbeJXWbBfU1usWcitCSR4XtECVo0nTP2nRQxWn5RXtYhFBdWH JKb9OzD9E9DT9Johyfmg3pdZOrzLAlE2tZROHoxY1UgLYIfy56QUBxN4O1GvIs25YlKO ZFsg== X-Gm-Message-State: ALoCoQlXhtsR0ufW/3IRN93WgGF3rv7FB48byQr3Zn/QeoAdzR4Sa7dBLaKCNtIi72UUGLLVvd3xduHBNBVZ7LhbjjpsestX7A== X-Received: by 10.140.218.72 with SMTP id o69mr42038470qhb.22.1453245883047; Tue, 19 Jan 2016 15:24:43 -0800 (PST) Received: from [192.168.1.177] (pool-173-78-77-162.tampfl.fios.verizon.net. [173.78.77.162]) by smtp.gmail.com with ESMTPSA id a5sm13138842qga.46.2016.01.19.15.24.42 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 19 Jan 2016 15:24:42 -0800 (PST) Sender: Davey Shafik Content-Type: multipart/alternative; boundary=Apple-Mail-A28C463D-39AD-4F8C-B823-5530BA2D0B16 Mime-Version: 1.0 (1.0) X-Mailer: iPad Mail (13C75) In-Reply-To: Date: Tue, 19 Jan 2016 18:24:41 -0500 Cc: "internals@lists.php.net" Content-Transfer-Encoding: 7bit Message-ID: <92406E0C-49DC-4A85-A9C5-98FB631D0A9B@php.net> References: To: Derick Rethans Subject: Re: [PHP-DEV] [RFC] Add HTTP/2 Support to the CLI Server From: davey@php.net (Davey Shafik) --Apple-Mail-A28C463D-39AD-4F8C-B823-5530BA2D0B16 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Jan 19, 2016, at 6:21 AM, Derick Rethans wrote: >=20 >> On Mon, 18 Jan 2016, Davey Shafik wrote: >>=20 >> Hey all, >>=20 >> following on from previous discussions[1], I am introducing an RFC for >> adding HTTP/2 support to the built-in CLI server: >>=20 >> https://wiki.php.net/rfc/cli_server_http2 >=20 > I think this is good to have, but I have a few comments: >=20 > php -S 0.0.0.0:8080 =E2=80=93http2 -t ./public/ ./public/index.html=20 >=20 > The -http2, should really be two --'s. Only short (one letter options)=20 > get a single '-'. >=20 > Similarly: =E2=80=93[no-]http2, should probably be either '--with-http2' a= nd/or=20 > '--without-http2', as it depends on an external library. I think my autocomplete replaced the two dashes with an emdash, oops. Yes, t= wo dashes for both. The --no-http flag is for turning off HTTP/2 when running the cli-server, if= it is enabled by default (as I think it should be), allowing you to test th= ings like fallback to HTTP/1.x for HTTP/2 clients. This is not a compile fla= g, that would definitely be --with or --without. >> Given that the RFC contains two potential solutions for implementing=20 >> this, I've decided it is best to open up discussion on this now. >>=20 >> While I've authored this RFC, I do not think I am capable of=20 >> implementing this, but I am going to try. I'm currently trying to get=20 >> to grips with the existing cli-server, and seeing if I can add H/2=20 >> support to the existing SAPI. However, it might be easier to just=20 >> write a new SAPI from scratch =E2=80=94 is there a good SAPI I can use as= an=20 >> example to learn that side of things? >>=20 >> Would anyone be interested in taking this on for 7.1? or=20 >> pairing/mentoring on it? >=20 > I don't think I have the time for that, but feel free to pop into IRC=20 > for questions. Thanks! - Davey - Davey > On Jan 19, 2016, at 6:21 AM, Derick Rethans wrote: >=20 >> On Mon, 18 Jan 2016, Davey Shafik wrote: >>=20 >> Hey all, >>=20 >> following on from previous discussions[1], I am introducing an RFC for >> adding HTTP/2 support to the built-in CLI server: >>=20 >> https://wiki.php.net/rfc/cli_server_http2 >=20 > I think this is good to have, but I have a few comments: >=20 > php -S 0.0.0.0:8080 =E2=80=93http2 -t ./public/ ./public/index.html=20 >=20 > The -http2, should really be two --'s. Only short (one letter options)=20 > get a single '-'. >=20 > Similarly: =E2=80=93[no-]http2, should probably be either '--with-http2' a= nd/or=20 > '--without-http2', as it depends on an external library. >=20 >> Given that the RFC contains two potential solutions for implementing=20 >> this, I've decided it is best to open up discussion on this now. >>=20 >> While I've authored this RFC, I do not think I am capable of=20 >> implementing this, but I am going to try. I'm currently trying to get=20 >> to grips with the existing cli-server, and seeing if I can add H/2=20 >> support to the existing SAPI. However, it might be easier to just=20 >> write a new SAPI from scratch =E2=80=94 is there a good SAPI I can use as= an=20 >> example to learn that side of things? >>=20 >> Would anyone be interested in taking this on for 7.1? or=20 >> pairing/mentoring on it? >=20 > I don't think I have the time for that, but feel free to pop into IRC=20 > for questions. >=20 > cheers, > Derick --Apple-Mail-A28C463D-39AD-4F8C-B823-5530BA2D0B16--