Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85585
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.182 as permitted sender)
MIME-Version: 1.0
Date: Tue, 31 Mar 2015 13:56:55 +0000
Message-ID: <CAH8MpnknSgzZEpsgqwfNMq5h8C5eM5RVREjvLwCA5YxLhMKc6Q@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>, gregory@luni.fr
Content-Type: multipart/alternative; boundary=001a113f6c4ec2217a051295f80e
Subject: Re: HTTP/2 and Websocket support in 7.x versions
From: rdlowrey@php.net (Daniel Lowrey)

--001a113f6c4ec2217a051295f80e
Content-Type: text/plain; charset=UTF-8

HTTP/2 is entirely outside the scope of the PHP web SAPI as it currently
exists. The protocol impacts the actual HTTP server and has nothing to do
with the SAPI runtime which is simply handed information about the HTTP
request once the server parses it. The protocol used to communicate those
details between the client and the HTTP server does not concern the web
SAPI. There is no need for any sort of "support for h2" in PHP; it's the
web server's concern. Apache and nginx will add support for h2 and PHP will
continue working as it always has.

That said, the php web SAPI derives exceedingly little benefit from the
advent of HTTP/2.0. h2 is designed to allow multiplexing of many requests
over the same TCP connection but the PHP web SAPI still has the same
bottleneck it had before h2: one thread/process per request.

As for websockets, you *can* do that using the web SAPI right now if you
wished but this would be inadvisable because long-lived connections will
quickly fill the bottleneck in every PHP web application (concurrent
threads/processes for each "request").

Instead, the appropriate solution for websockets would be to implement a
socket server directly in the CLI that speaks the websocket protocol.

Would it be useful to have raw incremental parsing functionality for
HTTP/1.1, HTTP/1.2 and websocket protocols available in userland? Sure, but
this falls more in the realm of an extension than anything else as few
people are implementing full-blown http and websocket servers in the CLI
right now.

--001a113f6c4ec2217a051295f80e--