Re: RFC: Server-Side Request and Response Objects (v2)

From: Date: Tue, 11 Feb 2020 16:58:40 +0000
Subject: Re: RFC: Server-Side Request and Response Objects (v2)
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-108489@lists.php.net to get a copy of this message
> On Feb 10, 2020, at 10:18, Paul M. Jones <pmjones@pmjones.io> wrote: > > Hi Internals, > > After a couple of years of incubation, I am happy to offer a second version of this RFC: > > https://wiki.php.net/rfc/request_response > > It proposes an object-oriented approach around request and response functionality already > existing in PHP, in order to reduce the global-state problems that come with superglobals and the > various response-related functions. > > The SQLite "about" page says, "Think of SQLite not as a replacement for Oracle > but as a replacement for fopen()." > <https://www.sqlite.org/about.html> Likewise, think of this > RFC not as a replacement for HttpFoundation or PSR-7, or as a model of HTTP messages, but as an > object-oriented alternative to superglobals, header(), setcookie(), setrawcookie(), and so on. > > Thanks in advance for your time and consideration while evaluating it. Regarding the array of arrays for $accept* and $forwarded, what are your thoughts on using value objects with properties, rather than arrays with keys? AcceptValue * string $value * string $quality * array $params * ?string $type * ?string $subtype ForwardedValue * string $by * string $for * string $host * string $proto Cheers, Ben

Attachment: [application/pgp-signature] Message signed with OpenPGP signature.asc
« previous php.internals (#108489) next »