Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:97669 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21697 invoked from network); 10 Jan 2017 20:11:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jan 2017 20:11:10 -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.161.181 cause and error) X-PHP-List-Original-Sender: me@daveyshafik.com X-Host-Fingerprint: 209.85.161.181 mail-yw0-f181.google.com Received: from [209.85.161.181] ([209.85.161.181:35822] helo=mail-yw0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 19/E7-55699-8DF35785 for ; Tue, 10 Jan 2017 15:11:08 -0500 Received: by mail-yw0-f181.google.com with SMTP id l19so11493177ywc.2 for ; Tue, 10 Jan 2017 12:11:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=daveyshafik-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=IdqpJtH4OppZyRwV+/5ZA5WbhNlPsbDWzIirf8k8X4w=; b=SAZUxWrCW8eTIFlCOpdyHvF9xKeCcfY22gON/y0nhfojd7RRj7Clp6TjP0Ast2/VKC Cf9mE3w7L57parnZx+hNhnbbiUNUW5pjkUjGcICfPRhN6kEJdT8sL+d9fPjllxjELcIx 5lkTjYW5jECediW1XYzp9WKHu+c6R2pHnjrxziXvvpmde/dsZtEtHoMW7hYB8IxR6PXd CleJLuHXE76v4t5VRTB8CLe2L0UPrMYeD41fGcyRQ4MoseVwBQMmtHSXEBHYrIhJqFcA 4GTDUSiOwm/p9NM6yA6z22OnhTWArNuysvaCD5wGlegkuPogTleo1q2INHjVuhoqQmMR n2sA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=IdqpJtH4OppZyRwV+/5ZA5WbhNlPsbDWzIirf8k8X4w=; b=jaZMXcq28uf72jaTS+l1hH9bm/70hrL08KOMQoGLI1SgwbuawxRjBO4NdS4yH4t8hm dzzgYpPjhmp11KoSh/xta4FCJSeeBwpYp5pPe7L9FzfNpf6NPrCzJ9PmqhdQaZOul2aQ pQFfThsqQoT03ujoqa4C/NsEr+WsJwWSL8OcurtU/Q3AvR++/csIuR9W2CrmiDKRE9Gn W1YjH41sSslSVY2pET+HobWU1pNpQIOi5DApEa61A8utM1rhh4JdrZXSVlueXdJO7w+i BxiaSxUgeueQHOr1Pi7jwv1Vwe9iwsxOqwTNUJglYUGR7LLWJQLyrmgSMvEO7/RWc2fc 1Iiw== X-Gm-Message-State: AIkVDXJmhmKVI/ukyW7bIIeFc0axKyfchn7bFn/QL54moU6oS8uSnPWKISFauUjBIjrTtiItamNAQK0WjM2QMC2Q X-Received: by 10.129.51.134 with SMTP id z128mr4210900ywz.352.1484079061079; Tue, 10 Jan 2017 12:11:01 -0800 (PST) MIME-Version: 1.0 Sender: me@daveyshafik.com Received: by 10.129.96.87 with HTTP; Tue, 10 Jan 2017 12:11:00 -0800 (PST) In-Reply-To: References: <0D275F6F-85D3-4E9D-AF89-03C91A23D5BD@gmail.com> Date: Tue, 10 Jan 2017 15:11:00 -0500 X-Google-Sender-Auth: aCmWPHvNh2-P4h7wVM3oaeXFmjY Message-ID: To: Paul Jones Cc: PHP Internals List Content-Type: multipart/alternative; boundary=001a114220dc415b9e0545c31543 Subject: Re: [PHP-DEV] [RFC][Discussion] ServerRequest and ServerResponse objects From: davey@php.net (Davey Shafik) --001a114220dc415b9e0545c31543 Content-Type: text/plain; charset=UTF-8 On Mon, Jan 9, 2017 at 10:43 AM, Paul Jones wrote: > > > On Jan 7, 2017, at 15:41, Joe Watkins wrote: > > > > That doesn't sound like a positive consensus that this is a good idea, > it is rather the opposite. > > Not to get into interpretations of comments, but while I agree that there > were one or two actual negatives, they were predicated on a > misunderstanding of the purpose of the RFC. As such I took them as neutral, > rather than negative. The remainder were questions or comments, and not > negative ones. > > Either way, I think we can see from reactions here since then (and > elsewhere) that there is some level of positive interest in the RFC as > presented, as well as some healthy technical questioning. I'm happy to hear > both. [Trying again, Sorry Paul who has likely received this three+ times nows] [Resent without URLs, grrr] Let me be absolutely clear: Any attempt to improve HTTP request/response handling in PHP that doesn't take into account WebSockets or HTTP/2 Server Push is a non-starter for me. PSR-7 was heavily influenced by Python's WSGI spec and they are also seeing it's inability to handle these types of interactions. As such there is a new recommendation being proposed called ASGI: Asynchronous Server Gateway Interface [1], that is intended to address this. I think it would be more beneficial for PHP the language to consider reaching out to the Python community and seeing if it makes sense to collaborate on this. A new ASGI SAPI would come with message objects/interfaces (see [1]) baked in. If we want PHP to have a meaningful presence for the future web, we need to move forward from our current request/response 1:1 HTTP-only model. So, as currently proposed, I'm -1. It doesn't move the language forward in any meaningful way. - Davey [1] google: ASGI python, it's the first result --001a114220dc415b9e0545c31543--