Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108864 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 54170 invoked from network); 5 Mar 2020 13:00:08 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Mar 2020 13:00:08 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7BD401804D3 for ; Thu, 5 Mar 2020 03:19:44 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f43.google.com (mail-wr1-f43.google.com [209.85.221.43]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 5 Mar 2020 03:19:40 -0800 (PST) Received: by mail-wr1-f43.google.com with SMTP id h9so6498607wrr.10 for ; Thu, 05 Mar 2020 03:19:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vXkEmEQ+7UA+V8uNESJsqX5t4U6JKZghr3D3DGUWDoo=; b=KJHsfb4vQUQkTDiEGICgbu0ZZmTkYL8lUfD2qXEVF6DfB/4nhrDnFVZdtBNS+h3ulx pjuXpGH69PGiPkNnFFhNxOffE68iWCsZpaC9GdcR0iwgD+VBDlecrMZV4S06E533hvNA hvmqI0UTr0jZi4TPF2S2ygnQGT/eO4NCg/b4QU1urnc2pEDUv3F3b8DqsAFgbY26hqfR Oweqyr9/NOISe0CduZgSyWDieyf/jY/DVMu6kxSYkVez6fkvUgS0ziLt6C3ScoJ/T9Zg o8W7eU3JnpOei/sblnW+DSbRnHn3o8606ga5Urw/C3BJjxsVB5PSDtu5PVaPYqkvaN3l EbVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vXkEmEQ+7UA+V8uNESJsqX5t4U6JKZghr3D3DGUWDoo=; b=AF5AJS26eL5rdHTnJESDCmXY73+tAYn9H7l0JPo5i1mW6j6wtZnhboWRKfoW7gHtHt RuLYCBtSfbr4+9aR3llVD7fYOmBFT668JHbMRUo6a0AkyWLmSsKr7Pmlk2F+b24z5JM5 UcCg+kllDaoY3wDRKIdNIQZHw2bsjWU5+narohDUVyQy6aRJkUMki2Acuu8SRZ3koaPH HGWSZV9uftljC0uNNkKGCCObOriTR6Qyv8oQFwWXgduEzaXM9u/pKHCXmQR7x7R27TpO dUZWxIt2ValALASTbbejc0ezsx9DKBHLgGVzcYTnydATSZ5q3dWwGVKy0PMjhTlH7En+ JrtA== X-Gm-Message-State: ANhLgQ0GTWukI1ndD5SNG0vQv+DQVy3WZugH4jgIoj1ISkXrGupacTbw 3wAJQSSyt3325UWy/P4W8UPRRaIQlKVUrsb72d0PIT68Pp0= X-Google-Smtp-Source: ADFU+vus1LGIV6MynGOSrrcxLmTzLgWVS9n74CtbGQR+9asIEvW0pAn+9rIIoqkCO1p/a1IxUhNRVeMWoCnERNRSAI8= X-Received: by 2002:adf:f686:: with SMTP id v6mr9310026wrp.176.1583407175243; Thu, 05 Mar 2020 03:19:35 -0800 (PST) MIME-Version: 1.0 References: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io> <1657AB79-5CAF-4BCA-96B5-1343EC703CCD@pmjones.io> In-Reply-To: <1657AB79-5CAF-4BCA-96B5-1343EC703CCD@pmjones.io> Date: Thu, 5 Mar 2020 12:19:08 +0100 Message-ID: To: "Paul M. Jones" Cc: php internals Content-Type: multipart/alternative; boundary="000000000000371c9f05a019b6e4" Subject: Re: [PHP-DEV] RFC: Server-Side Request and Response Objects (v2) From: arvids.godjuks@gmail.com (Arvids Godjuks) --000000000000371c9f05a019b6e4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 28 Feb 2020 at 16:25, Paul M. Jones wrote: > Hi everyone, > > All outstanding issues on this RFC appear to be resolved one way or > another. With that in mind: > > Are there any members here who currently expect to vote "no", who have no= t > yet chimed in? I'd like to hear your criticisms and objections, so I can = at > least attempt to resolve your concerns. > > I am especially interested to hear about technical or developer-experienc= e > shortcomings, but of course variations on "this is better left to userlan= d" > are understandable. > > Again, and as always, my thanks for your time and attention. > > > -- > Paul M. Jones > pmjones@pmjones.io > http://paul-m-jones.com > > Modernizing Legacy Applications in PHP > https://leanpub.com/mlaphp > > Solving the N+1 Problem in PHP > https://leanpub.com/sn1php > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Hello Paul, one question I do have here is about how PHP-PM process manager will be able to interact with this layer? Cause right now it does rewrite the $_SERVER variable for each incoming request for its child processes that handle the requests https://github.com/php-pm/php-pm/blob/a2872e13c3901401d5c2386a8ed62502db23d= 5f2/src/ProcessSlave.php#L463 It kind'a makes this not possible if there is no way to re-init the object. While read-only is, obviously, a good idea, there are some caveats like this that not only limit the possibilities but also what will the ServerRequest object even look like when $_SERVER is being rewritten like this? They relly on https://github.com/php-pm/php-pm-httpkernel package to handle the GET/POST/COOKIE/SESSION data for each supported framework trying to avoid the usage of the superglobals, but I see $_COOKIE being used. This, in turn, relies on https://github.com/guzzle/psr7/ and that one reads the data from the $_GET/$_POST/$_FILES the data: https://github.com/guzzle/psr7/blob/c8676a22904ebc3143b8485364cbe9ac97dc3f3= e/src/ServerRequest.php#L170 Basically to put in in a single sentence - so far it seems that this RFC does not allow such usage at all and long-running processing has not been taken into account at all? Thanks! --=20 Arv=C4=ABds Godjuks +371 26 851 664 arvids.godjuks@gmail.com Skype: psihius Telegram: @psihius https://t.me/psihius --000000000000371c9f05a019b6e4--