I actually agree with that. I've reached a point when I consider using fsockopen instead of curl to fetch information from a website. I can hardly stand cURL.
There should be a decent OOP based wrapper for making HTTP requests to handle it decently. Meanwhile, I agree that cURL needs to go. On Mon, Apr 1, 2013 at 2:18 AM, Hannes Magnusson <hannes.magnus...@gmail.com> wrote: > On Sun, Mar 31, 2013 at 6:25 AM, Laruence <larue...@php.net> wrote: >> Hey: >> >> there are some issues when people run some codes in a php which is >> compiled with --with-curlwrappers, like #61336, or the recently test script >> for #64433 (failed when curl wrappers enabled). >> >> I know, that the curl wrapper should act the same as php http wrapper, >> but for now, we need to provide the ability to user, that they can warn if >> they codes can not run with curl wrappers.. >> >> here are some really usages: >> https://github.com/UnionOfRAD/lithium/issues/59 and >> http://weizhifeng.net/wrong-with-curlwrappers.html >> >> I propose to add a constant : bool CURL_WRAPPERS_ENABLE > > The curl wrappers have always been a major pain, with plenty of bugs > and we tend to forget to add context options there to match the > standard wrapper on new feature. > > It has been marked as experimental since forever, and I think its time > to face the failed experiment and remove it. > > -Hannes > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
