Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108720
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Date: Sat, 22 Feb 2020 09:23:05 -0600
References: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io>
 <50CF1E61-1EF9-4D2C-AEE2-D98E1CFF6F40@pmjones.io>
To: php internals <internals@lists.php.net>
In-Reply-To: <50CF1E61-1EF9-4D2C-AEE2-D98E1CFF6F40@pmjones.io>
Message-ID: <780D9DFF-AA82-4FF5-9EED-CAEEEE2337F5@pmjones.io>
Subject: Re: [PHP-DEV] RFC: Server-Side Request and Response Objects (v2)
From: pmjones@pmjones.io ("Paul M. Jones")

Hi all,

Off-list discussion with some vendors and consumers indicates that =
adoption and migration might be eased by the following changes to =
ServerResponseInterface:

- Add the following methods:

    - `getHeader(string $label) : ?string`
    - `hasHeader(string $label) : bool`
    - `getCookie(string $name) : ?array`
    - `hasCookie(string $name) : bool`

- Modify `add*()`, `set*()`, and `unset*()` to be fluent (allow method =
chaining)

Since these changes fit in well with the RFC goals, and do not =
substantially modify prior usage expectations, John Boehr has applied =
them to the extension, with documentation and tests.

Further, one evaluator noted that ServerResponseSender::sendContent() =
did not allow for iterables/generators as content; that has been =
remedied as well.


--=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