Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108585
MIME-Version: 1.0
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>
In-Reply-To: <CA+hqhpcOqCqXuOh3bWavJ+pZ5VVhekUO9LkKgd9c+b98VVnZSA@mail.gmail.com>
Date: Fri, 14 Feb 2020 17:47:39 +0100
Message-ID: <CAG9XoMRm2Nqjg3UbCc5=1_8m2W7qf8QRoSVk6d_qENJCKE1=9A@mail.gmail.com>
To: Bruce Weirdan <weirdan@gmail.com>
Cc: "Paul M. Jones" <pmjones@pmjones.io>, 
	=?UTF-8?Q?C=C3=B4me_Chilliet?= <come.chilliet@fusiondirectory.org>, 
	Niklas Keller <me@kelunik.com>, PHP Development <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000058e644059e8bf7ae"
Subject: Re: [PHP-DEV] RFC: Server-Side Request and Response Objects (v2)
From: benjamin.morel@gmail.com (Benjamin Morel)

--00000000000058e644059e8bf7ae
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
> What about $query and $body? That would be closer to the terminology
> used in HTTP RFCs.



The problem is that $body is typically used to get the raw message body as
a string or stream.
I was thinking more something along the lines of $bodyParams, which is more
verbose but leaves no ambiguity: *$queryParams* and *$bodyParams*.

=E2=80=94 Benjamin

--00000000000058e644059e8bf7ae--