Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121260
MIME-Version: 1.0
References: <65208c89.250a0220.3ebd5.0948SMTPIN_ADDED_MISSING@mx.google.com> <4AD2C29F-FD37-49D0-AA61-B91740231067@gmail.com>
In-Reply-To: <4AD2C29F-FD37-49D0-AA61-B91740231067@gmail.com>
Date: Sat, 7 Oct 2023 06:53:23 +0200
Message-ID: <CABdc3WrWMhPJ3rAuUnu1hrLVnX3Ww7UKt-=WXqTZrDbHxJwyLQ@mail.gmail.com>
To: =?UTF-8?Q?Marco_Aur=C3=A9lio_Deleu?= <deleugyn@gmail.com>
Cc: Ben Ramsey <ramsey@php.net>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000b6db4b06071923c0"
Subject: Re: [PHP-DEV] [RFC][Under discussion] RFC1867 for non-POST HTTP verbs
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--000000000000b6db4b06071923c0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Marco,

sob., 7 pa=C5=BA 2023 o 00:55 Marco Aur=C3=A9lio Deleu <deleugyn@gmail.com>
napisa=C5=82(a):

> Just wanted to mention that maybe this is a great opportunity to create a
> request_ family and start with request_parse_post_data
>

My first thought was why the word `_post_` and not for instance instead
a`_form_` which better expresses the purpose then?
I'd avoid using the "post" word if we tend to provide functionality that is
common for other HTTP methods which in fact was the preliminary cause of
this discussion.

Cheers,
Micha=C5=82 Marcin Brzuchalski

--000000000000b6db4b06071923c0--