curl/docs
2000-06-08 15:20:03 +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
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_perform.3 updated 2000-05-26 11:59:43 +00:00
curl_easy_setopt.3 Added progress callback info 2000-06-08 15:13:41 +00:00
curl_formparse.3 Added description 2000-06-06 14:54:42 +00:00
curl_getdate.3 added description 2000-06-02 10:50:09 +00:00
curl_getenv.3 Added description 2000-06-02 11:01:08 +00:00
curl_slist_append.3 added description 2000-06-02 11:31:18 +00:00
curl_slist_free_all.3 Added description 2000-06-02 11:34:17 +00:00
curl_version.3 Added description 2000-06-02 11:34:17 +00:00
curl.1 updated 2000-05-29 22:54:17 +00:00
FAQ edited to look better after the txt2html convertion 2000-06-06 14:13:36 +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 Added text about how to convert certificates to PEM format 2000-06-05 08:21:28 +00:00
README.libcurl updated 2000-05-26 11:59:43 +00:00
RESOURCES moved here from the root directory 2000-05-22 17:35:35 +00:00
TODO the recent mocking 2000-06-08 15:20:03 +00:00

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


                     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.

The Easy Interface

 When using the easy interface, you init your easy-session and get a handle,
 which you use as input to the following interface functions you use.

 You continue be setting all the options you want in the upcoming transfer,
 most important among them is the URL itself. You might want to set some
 callbacks as well that will be called from the library when data is available
 etc.

 When all is setup, you tell libcurl to perform the transfer. It will then do
 the entire operation and won't return until it is done or failed.

 After the performance is made, you cleanup the easy-session's handle and
 libcurl is entire off the hook!

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

        curl_easy_init() 
        curl_easy_setopt() 
        curl_easy_perform() 
        curl_easy_cleanup()