Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90721
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain daveyshafik.com from 209.85.160.172 cause and error)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
In-Reply-To: <alpine.DEB.2.20.1601191117210.3314@whisky.home.derickrethans.nl>
Date: Tue, 19 Jan 2016 18:09:05 -0500
Cc: Davey Shafik <davey@php.net>,
 "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <4D207EB1-F0CF-4E0A-B31F-E733E95CB3BA@daveyshafik.com>
References: <CANaX5necU5mdMLekU68CSgxFNTLZzUjB=XcHP0vtEH+cu5XyGA@mail.gmail.com> <alpine.DEB.2.20.1601191117210.3314@whisky.home.derickrethans.nl>
To: Derick Rethans <derick@php.net>
Subject: Re: [PHP-DEV] [RFC] Add HTTP/2 Support to the CLI Server
From: me@daveyshafik.com (Davey Shafik)

On Jan 19, 2016, at 6:21 AM, Derick Rethans <derick@php.net> 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