HTTP message interfaces & factories (PSR-7/17)

[MGatner]

At some point we should make sure we are implementing these compliance definitions:

• https://www.php-fig.org/psr/psr-7/
• https://www.php-fig.org/psr/psr-17/

[agungsugiarto]

Suggested using
• https://github.com/laminas/laminas-diactoros
• https://github.com/slimphp/Slim-Psr7

[tada5hi]

What is the status about this @MGatner ? Are you working on it or should i do a pr? 😇✌️

[agungsugiarto]

ping @MGatner

[MGatner]

I'm not actively working on this. I started a couple weeks back and determined it should not be too much work.

[tada5hi]

so @MGatner you will catch it up later or should i just go ahead?

[MGatner]

If you can implement it then please go ahead and do so! I will not be working on this for a while.

[tada5hi]

@MGatner thx, i think so 😄 . I will try to keep backwards compatible.

[MGatner]

@tada5hi No pressure but I'm gathering some info for 4.1 - do you think this will be done this week?

[asrofie]

Hi Team,
Anyone still working on this ?
If no one, I want to try handle it.

[MGatner]

Nobody is working on it actively, please do! Familiarize yourself with the existing PRs and the conversations on those. The tricky part, if I recall, is that our version of Message has getHeader() and getHeaders() which do not comply with PSR-7 (because they return Header). However since then I think we figured out that we could make Header stringable and still comply.

Regardless pay attention that no breaking changes are made, and leverage those HTTP Integration tests (so you shouldn't have to write many!).

[MGatner]

Also, if you determine that this won't fit in the core framework you can compare what I did with PSR Cache and Simple Cache: https://github.com/codeigniter4/cache

We could definitely add HTTP as a separate module

[asrofie]

Oke, I will create implementation first.