Hi Michael, > On 28 Jan 2015, at 19:48, Michael Wallner <m...@php.net> wrote: > > On 28/01/15 20:18, Andrea Faulds wrote: >> >> If the client is merely a wrapper around cURL, what benefit does it >> offer over ext/curl except a better API? >> >> Personally, I’ve never liked that PHP requires cURL for doing HTTP >> requests. It’s a language made for the web, it should have built-in >> HTTP, and it should share code between its server-side HTTP and >> client-side HTTP stuff. I don’t think that the HTTP stream wrappers >> are a “hack” - they’re what PHP should have had all along. I think we >> should focus on improving them (so there’s no need to use cURL) >> rather than adding yet another HTTP client. > > Sounds a bit like NIH.
Ah, no, I hope I’m not misunderstood that way. My objection to cURL is that I don’t feel we should be using separate codebases for HTTP client stuff vs. HTTP server stuff. It doesn’t feel right to me that in such a web-focussed language we should have to use an external library for making HTTP requests - why can’t we use PHP’s own HTTP capabilities? IMO, they should be a single codebase. It’s needless duplication otherwise. Thanks. -- Andrea Faulds http://ajf.me/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
