-
-
Notifications
You must be signed in to change notification settings - Fork 598
[POC] [WIP] Abstract the HTTP Client by using HTTPlug #352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
25504c9
to
e0f19f7
Compare
👎 for the idea from me. |
@GrahamCampbell Thanks for the feedback :) Can you explain why ? |
I just feel that guzzle 5/6 does a good job by itself. I see no advantage to adding yet another library on top that might suffer the same upgrading problems to newer libraries that we already do. |
@GrahamCampbell I understand, I feel the same. The problem we tried to solve with this is the fact we were bound to an old version of guzzle ( In addition, we will have the guzzle 5+ http cache plugin for free, which is very cool. |
Httplug is an abstraction for any http client. Using an abstraction means that you decouple yourself from the implementation. This is the D in SOLID, dependency inversion principle. We should not exclude users using Guzzle5 by require Guzzle6, right? If someone do not want to use Guzzle at all but pure cURL instead should we force them to do otherwise? No. Authors of I have made some contributions to the php-http organisation and I am happy to help migrating |
@Nyholm you may fork this PR if you are interested. |
@cursedcoder Are you interested in this feature if I finish the PR? |
@Nyholm it would be great if you can finish it. |
Thank you. I'll add this on my TODO list =) |
I forgot to ping this thread. Here are the new PR: #389 |
No description provided.