Hi! > 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
I see no problem in depending on cURL. NIH'ing every part of the software universe in unfeasible, and if somebody does this one job and does it well - why not use it? We don't have enough resources here to implement every detail of the huge protocol like HTTP, and that's the whole point of opensource to reuse and combine projects. > 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 HTTP stream wrappers work for some cases, but not for all and for cases where you need deep involvement with details of HTTP - like headers, byteranges, content encodings, etc. - they might not be the best API to deal with it. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
