curl/docs
Daniel Stenberg 285994a5ae slightly adjusted 2000-05-22 19:10:53 +00:00
..
BUGS moved here from the root directory 2000-05-22 17:35:35 +00:00
CONTRIBUTE moved here from the root directory 2000-05-22 17:35:35 +00:00
FAQ moved here from the root directory 2000-05-22 17:35:35 +00:00
FEATURES moved here from the root directory 2000-05-22 17:35:35 +00:00
INSTALL slightly adjusted 2000-05-22 19:10:53 +00:00
INTERNALS moved here from the root directory 2000-05-22 17:35:35 +00:00
README.curl moved here from the root directory 2000-05-22 17:35:35 +00:00
README.libcurl libcurl v7 adjustments 2000-05-22 19:02:54 +00:00
RESOURCES moved here from the root directory 2000-05-22 17:35:35 +00:00
TODO moved here from the root directory 2000-05-22 17:35:35 +00:00
curl.1 slightly adjusted 2000-05-22 19:10:53 +00:00
curl_easy_cleanup.3 libcurl v7 adjustments 2000-05-22 19:02:54 +00:00
curl_easy_init.3 libcurl v7 adjustments 2000-05-22 19:02:54 +00:00
curl_easy_setopt.3 libcurl v7 adjustments 2000-05-22 19:02:54 +00:00

README.libcurl

                         _ _ _                     _ 
                        | (_) |__   ___ _   _ _ __| |
                        | | | '_ \ / __| | | | '__| |
                        | | | |_) | (__| |_| | |  | |
                        |_|_|_.__/ \___|\__,_|_|  |_|


                     How To Use Libcurl In Your Program

Interfaces

 libcurl currently offers two different interfaces to the URL transfer
 engine. They can be seen as one low-level and one high-level, in the sense
 that the low-level one will allow you to deal with a lot more details but on
 the other hand not offer as many fancy features (such as Location:
 following). The high-level interface is supposed to be a built-in
 implementation of the low-level interface. You will not be able to mix
 function calls from the different layers.

 As we currently ONLY support the high-level interface, the so called easy
 interface, I will not attempt to describe any low-level functions at this
 point.

Function descriptions

 The interface is meant to be very simple for very simple
 implementations. Thus, we have minimized the number of entries.

Main Operations

 You INIT the lib

 You SET OPTIONS you want the lib to use.

 You tell the lib to PERFORM the transfer.

 You CLEAN UP the lib

 done.

 See the separate man pages for the libcurl functions for details.


        CURLcode curl_easy_setopt(CURL *curl, CURLoption option, ...);



CURLcode curl_easy_perform(CURL *curl);
void curl_easy_cleanup(CURL *curl);