PHPDeveloper.org

PHPBuilder.com: Transfer Data via Multiple Protocols with Libcurl

Mon, 19 Sep 2011 12:03:23 -0500

On PHPBuilder.com today there's a new tutorial showing how to use libcurl to communicate with multiple protocols like FTP, HTTP, HTTPS, SMTP and STMPS. The libcurl library that can be compiled in or installed as a shared module in your PHP install to provide enhanced networking abilities.

As I wrote in my PHP multithreading with cURL article, the libcurl is a free and easy-to-use client-side URL transfer library, supporting DICT, FILE, FTP, FTPS, GOPHER, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, POP3, POP3S, RTMP, RTSP, SCP, SFTP, SMTP, SMTPS, TELNET and TFTP. PHP supports the libcurl library which allows you to connect and communicate to many different types of servers with many different types of protocols.

The tutorial focuses on two different types of connections (well, four really) - FTP/FTPS and HTTP/HTTPS - and how to transfer data across each. Some code is included to create a (procedural) tool to send an uploaded file to a remote site.

Mike Wallner's Blog: Introducing libcurls multi socket API

Tue, 11 Sep 2007 13:48:44 -0500

Mike Wallner has announced the release of the first beta of the pecl_http PECL package, an extension that "aims to provide a convenient and powerful set of functionality for one of PHPs major applications."

So, finally a first beta of pecl_http 1.6 has been released. This is the first version which supports libcurls multi socket API introduced in 7.16 through libevent.

The rest of the post shows stats comparing the timing on a normal connection versus using the multi-socket API (on both an empty file and a 100k file).

Mike Wallner's Blog: Cookie Handling

Mon, 22 May 2006 06:03:47 -0500

Mike Wallner is sharing a quick note in this new blog post about some "weirdance" he noticed while working with libcurl and cookies.

I had to implement some changes which are only in CVS for now. Beware that all this does not affect custom cookies set with HttpRequest::setCookies() and HttpRequest::addCookies(). Custom cookies can always be unset by calling HttpRequest::setCookies().

He's made these adjustments in the CVS for the library, and mentions an implementation of the cookiestore option with these new changes as well.