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
