Description: ------------ A new E_STRICT-compatible version of HTTP_Request package [1] has been released, please consider using it instead of relying on cURL extension. If HTTP_Request2 is not yet ready for your package's needs, do not hesitate to open requests for missing features. [1] http://pear.php.net/package/HTTP_Request2/

See also Bug #15855

This blocks me from mocking out unit tests in Services_Youtube for it's XML_RPC2 driver. If it doesn't get fixed soon, I might drop the XML_RPC2 driver - thoughts?

Thank you for your bug report. This issue has been fixed in the latest released version of the package, which you can download at http://pear.php.net/get/

Sérgio, I reviewed your changes @ http://svn.php.net/viewvc/pear/packages/XML_RPC2/trunk/XML/RPC2/Util/HTTPRequest.php?revision=308648&view=markup The suggested approach when working with HTTP_Request2 is to accept a "template" instance of said class and then clone it and populate with actual request data before performing the request. This way a user can setup the request class in any way he likes (adapter, proxies, auth, other parameters...) and you don't have to duplicate all possible setup in your own class as you currently do. This also allows using Mock adapter with pre-populated responses, as was the point of request #15855

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. Implemented pre-populated HTTP_Request2 instance as an option of XML_RPC2_Client (option 'httpRequest'). Ideally, XML_RPC2_Util_HttpRequest should be dropped, but that is a larger refactoring than I'm willing to endeavour now, and one that will imply a major API change. Options such as handling of SSL, timeouts or proxies will be left out of XML_RPC2 and moved into the concern area of HTTP_Request2. Right now, settings that are handled by XML_RPC2 (ssl, timeouts, proxies) will be reset on the pre-populated HTTP_Request2 instance that is provided. All other settings are left as-is.