-
Notifications
You must be signed in to change notification settings - Fork 85
Version 3.0/PSR-7 integration? #13
Comments
For migration purposes, we will be keeping the component essentially as-is. The ZF2 MVC utilizes this component heavily, and we do not want to make migration from 2 to 3 difficult for MVC applications. Additionally, the HTTP client predates Guzzle by several years, and is in use in a large number of applications; we do not want to make migration too difficult. We will likely steer people towards PSR-7 implementations in the future, and I expect we'll take some of the header implementations here and migrate them to another library for folks to consume; however, we'll keep them intact here for existing users. Otherwise, this component will not have active development going forward. |
Thanks for your explanation. So, if I understand it correctly, ZF3 MVC will still be based on I was asking, because I'm actually already using part of this library in my PSR-7 project, but it just feels bad to include full Is there anything that can be done to make this separate header library sooner than later? I don't think there is a PSR-7 library like this around, and likely the demand will rise soon (even for Apigility 2.0?). |
there is https://github.com/zendframework/zend-psr7bridge for it, it can be closed. |
This repository has been closed and moved to laminas/laminas-http; a new issue has been opened at laminas/laminas-http#26. |
Dear ZF Team,
Is there a roadmap or plans for version 3.0 of this component, making it PSR-7 compilant?
Thinking about it, I can see 3 major responsibilities of this repo:
With
zend-diactoros
covering "HTTP message",zend-http
could be ultimately split into two repositories. A lot of PSR-7 applications could benefit from good header manipulation library (I didn't see anything like this centered around PSR-7 yet), that can be developed without spending time on migrating the client (well, we have Guzzle).What do you think?
best,
The text was updated successfully, but these errors were encountered: