On Thu, Apr 4, 2013 at 11:27 AM, Pierrick Charron <pierr...@adoy.net> wrote:
> Hi
>
> I don't think we should remove curlwrappers from 5.5. I do agree that this
> is not yet stable and ready to push as non experimental, but since we plan
> to release 5.5 soon I don't think removing it right now is worth it.
>
> I started some time ago to maintain the curl extension. I focused mainly on
> adding to ext/curl all options from the libcurl api that were not available
> in PHP userspace. I also fixed some bugs on curlwrappers and will be please
> to fix (or at least try to fix) all bugs that we may have with curl and curl
> wrappers in the hope that it will be stable enough to be release with php
> nexté
>
> If you have a bug with curlwrapper (or anything related to ext/curl) please
> assign me the bug on the tracker and I will try to look at them ASAP.
Its not only about maintaining it.
This experiment failed a long time ago. Overwriting the core streams
has proven itself to be the wrong way.
If there was a way for userspace to say "overload with curl" then thats fine.
We already have a procedure for this:
stream_wrapper_unregister("http");
stream_wrapper_register("http", "CurlStreamWrapper");
and then stream_wrapper_restore("http") to go back to the core streams.
I would definitely see the benefits in something like that, but as
things are now are simply not working and should be removed.
The "real way" can be re-implemented later.
-Hannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
