You can also use cURL as adapter for Zend_Http_Client. There is a
version in the SVN incubator.
The Socket Adapter of Zend_Http_Client has far less functionality
than cURL. You need Zend_Http_Client for certain components that rely
on it (Service_* for example, Zend_Rest).
On Mon, 22 Dec 2008 00:57:11 +0100, till klimp...@gmail.com wrote:
On Mon, Dec 22, 2008 at 12:23 AM, Luiz A Brandao Jr fromv...@gmail.com
wrote:
Hello,
What's the reason to use Zend_Http_Client over the cURL extension?
Do you know how Zend_Http_Client performs comparatively to curl?
Thank you,
Luiz
If performance is your #1 priority over maintainable code then it's
probably cURL. Just benchmark it.
However the advantage you gain by using the Zend class is a very easy
API, easy customization (through options and by extending the API),
etc. pp.. You can't really compare the two. Point taken, you can use
both to get the job done, but Zend_Http_Client provides a lot of
convenience which you don't get with pure PHP/cURL -- as usually when
you turn to a framework.
Also, by default Zend_Http_Client uses sockets -- which are
omnipresent in 99% of all PHP installs, whereas cURL is not always
around.
Till
