Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120707
MIME-Version: 1.0
References: <CAPyj-LAabBCvrHUTgO4yoJATmvT0N2Kk7ZpwCb=Vo9aRbz7PtQ@mail.gmail.com>
 <CALKiJKoQudehGwZF9OrB=+rpmpz4My7WR3Fx34GUN2XZL9J1nQ@mail.gmail.com>
 <E7C8FDCD-4333-4D7A-BBB3-C365F9F1D8CA@benramsey.com> <CAPyj-LDnkR+8Y3owNbtT1vgVtBJADE+Y1GTWMiZ8jDSxOZhUgA@mail.gmail.com>
 <15D6E65D-97E3-4F82-8C8A-B8C1FB22D972@benramsey.com> <8FB3E9E9-7240-45BE-B060-C4ACCEDFDC50@koalephant.com>
 <06cefa3c-a314-415a-9f69-619ddc24b72d@app.fastmail.com> <e3d80466-2f79-46f6-7c49-b60f5febe463@heigl.org>
In-Reply-To: <e3d80466-2f79-46f6-7c49-b60f5febe463@heigl.org>
Date: Wed, 28 Jun 2023 08:18:37 +0200
Message-ID: <CABdc3Wo6Se8PevhidYbC5ivH3VJht-i8x9+T45NVJ9Kvqmw6+A@mail.gmail.com>
To: Andreas Heigl <andreas@heigl.org>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000aa949205ff2a8e71"
Subject: Re: [PHP-DEV] RFC1867 (multipart/form-data) PUT requests
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--000000000000aa949205ff2a8e71
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Andreas,

=C5=9Br., 28 cze 2023 o 07:55 Andreas Heigl <andreas@heigl.org> napisa=C5=
=82(a):

> ...
> While I like not adding more Superglobals, it seems like we are adding
> more and more functions to retrieve the different parts of a
> Request-Object...
>
> So when we are at it: Why don't we introduce exactly that? A
> Request-Object that has all the methods. And which is immutable.
>
> And one method `request(): \Request`
>

I agree with the above, this would allow us to clean up the global
namespace in the future.
My personal use cases for PHP are mostly queue workers/event stream
consumers,
so the usual request/response model SAPI is used rarely. But I understand
that it's not the most used case.
Adding a couple of additional functions to a set of already ones just adds
more symbols not always used.
Ideally, I'd see an HTTP module in the future enabled in
request/response-oriented SAPI but that's a different story.


>
> I deliberately didn't call it `getRequest` (or `get_request`) to not
> confuse people why there isn't also a `post_request` or `put_request` or
> ... you get the picture)
>
> One additional function in global namespace and then we can use one of
> the request-objects that are already out in the wild. I don't think
> there's a need to invent the wheel again.
>
> The advantage might be that no matter how many calls to `request()` you
> will always get the same result. The Request as it came in.
>

That sounds like a use for a const?!

Just my .50=E2=82=AC

Cheers,
Micha=C5=82 Marcin Brzuchalski

--000000000000aa949205ff2a8e71--