Hi all,

> On Jul 2, 2025, at 12:41, Larry Garfield <la...@garfieldtech.com> wrote:
> 
> On Wed, Jul 2, 2025, at 12:34 PM, Paul M. Jones wrote:
>> Hi all,
>> 
>>> The question of PHP-native request/response objects has come up a couple of 
>>> times, and even had an RFC that went to a vote (declined).  My stance has 
>>> been, and remains, that ... they should be powerful enough to effectively 
>>> replace/displace PSR-7.
>> 
>> Where and when have you previously articulated that stance? Because I'd 
>> be thrilled to re-open yet another version (the 3rd) of that RFC.
>> 
>> -- pmj
> 
> I believe I stated it (perhaps phrased differently, it's been a while) in the 
> discussion thread of your previous RFC.

You commented three times in that thread; the relevant one appears to be the 
second, and includes Symfony's HttpFoundation:

- https://externals.io/message/108436#108591

- https://externals.io/message/108436#108838 "I would be very much in favor of 
a proposal that goes much further, with the aim that it can eventually 
deprecate PSR-7 and HttpFoundation, or at least large portions of them."

- https://externals.io/message/108436#109007

I included that sentiment under "Disruptive to (or insufficiently unifying of) 
userland ecosystem" in the after-action on that RFC: 
<https://externals.io/message/109563>.

To sum up: your position is that any HTTP-related offering here must be able to 
supplant both PSR-7 and HttpFoundation? 

Further: now that Symfony has its own HttpClient, should that be supplanted as 
well?


> And voted against the RFC on the grounds that I didn't feel it was robust 
> enough to effectively replace PSR-7 and HttpFoundation.

You were not a voter at the time. Memories fade, I guess.


-- pmj

Reply via email to