Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108589
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
In-Reply-To: <CAG9XoMRm2Nqjg3UbCc5=1_8m2W7qf8QRoSVk6d_qENJCKE1=9A@mail.gmail.com>
Date: Fri, 14 Feb 2020 16:12:24 -0600
Cc: Bruce Weirdan <weirdan@gmail.com>,
 =?utf-8?Q?C=C3=B4me_Chilliet?= <come.chilliet@fusiondirectory.org>,
 Niklas Keller <me@kelunik.com>,
 PHP Development <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EED3B438-6036-4A3A-A1E4-CE32FC2379CF@pmjones.io>
References: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io>
 <CANUQDCiP31aEqULqeGpN66ESHarKxWuXgQt_CqWeCLZc+1L-fA@mail.gmail.com>
 <5904137.fSVIMsojiJ@mcmic-probook>
 <CDBA02D0-07E1-4723-947C-22B403E650C0@pmjones.io>
 <CA+hqhpcOqCqXuOh3bWavJ+pZ5VVhekUO9LkKgd9c+b98VVnZSA@mail.gmail.com>
 <CAG9XoMRm2Nqjg3UbCc5=1_8m2W7qf8QRoSVk6d_qENJCKE1=9A@mail.gmail.com>
To: Benjamin Morel <benjamin.morel@gmail.com>
Subject: Re: [PHP-DEV] RFC: Server-Side Request and Response Objects (v2)
From: pmjones@pmjones.io ("Paul M. Jones")

Hi all,

> On Feb 14, 2020, at 10:47, Benjamin Morel <benjamin.morel@gmail.com> =
wrote:
>=20
>>=20
>> What about $query and $body? That would be closer to the terminology
>> used in HTTP RFCs.
>=20
>=20
> The problem is that $body is typically used to get the raw message =
body as
> a string or stream.
>=20
> I was thinking more something along the lines of $bodyParams, which is =
more
> verbose but leaves no ambiguity: *$queryParams* and *$bodyParams*.

I get the desire to disambiguate. But as an added consideration, there's =
a desire for consistency; when adding a -Params suffix to those names, =
it might then make sense to have $serverParams, $cookieParams, etc.

Looking at it that way, I don't think a -Params suffix is necessary. I =
would think $query would be enough.

As for the other name, the one for the $_POST equivalent, $body doesn't =
seem quite right to me; it seems a little close to $content.  I've also =
been thinking about $values, $params, $parsedContent, $contentValues, =
$bodyValues, $contentArray, and other variations with and without =
prefixes and suffixes, but $input is the one that feels like the =
least-terrible alternative to $post for me, esp. given the connection to =
php://input.


--=20
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