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. Thanks Pierrick On 4 April 2013 09:49, Julien Pauli <jpa...@php.net> wrote: > IMO , we should remove that feature from 5.5. > > If Laruence is OK to maintain it, then we keep it, but Laruence, please, > improve it so. > We keep it if Laruence can make it stable for 5.5 final. If he cant , or > doesn't want to work on it any more while in betas ; then we should remove > curlwrapper from 5.5. > > Laruence: If you (or someone else) are motivated to work on it and feel all > right to turn it to a stable feature without breaking streams or other > stuff , then we will discuss a way to detect it. > > Why not parse the configure options by adding a new way to do it ? > I'm writing a mail about that now. > > Thanks. > > Julien.P >