Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100841
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.53 as permitted sender)
MIME-Version: 1.0
Date: Mon, 9 Oct 2017 13:20:30 +0200
Message-ID: <CAOWwgpnS0x=YdZytA1chLKU9uoGmbaHs8Zb0E4M2p-0B_36dRQ@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a113c6f2211d217055b1b6239"
Subject: Session extension cannot be used in a loop/CLI since 7.2
From: nicolas.grekas@gmail.com (Nicolas Grekas)

--001a113c6f2211d217055b1b6239
Content-Type: text/plain; charset="UTF-8"

Hello,

I'm having a hard time fixing Symfony's tests suite to 7.2 because of the
added warnings+ini_set-rejections in the Session module.

Testing the session on the CLI is not possible anymore without starting one
PHP process per test case. Why not, you may say.

BUT, this also means that the session module is now basically useless in a
request-response loop.
That means ReactPHP, PHP-PM, Amp & the likes are all going to have to
rewrite a userland session module completely. That also means e.g. Symfony
and all other frameworks will have to move away from the internal's Session
module if they want to work also with these long living processing model.

PHP is less "generic" now - with stronger bindings to its short lived
req/resp. cycle.
Is it something internal should care about? Should we reconsider this for
7.2?

Regards,
Nicolas

--001a113c6f2211d217055b1b6239--