moparisthebest
/
curl
mirror of https://github.com/moparisthebest/curl
1
0
Fork 0
Code Issues Releases Wiki Activity

refer to function names better to enhance the HTML output

This commit is contained in:
Daniel Stenberg 2004-03-15 11:56:07 +00:00
parent 8f77030473
commit 8c4e91a653
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
docs/libcurl/libcurl.3
View File

@ -15,13 +15,13 @@ further reading on how to do programming with libcurl.
There exist more than a dozen custom bindings that bring libcurl access to There exist more than a dozen custom bindings that bring libcurl access to
your favourite language. Look elsewhere for documentation on those. your favourite language. Look elsewhere for documentation on those.
All applications that use libcurl should call \fIcurl_global_init()\fP exactly All applications that use libcurl should call \fIcurl_global_init(3)\fP
once before any libcurl function can be used. After all usage of libcurl is exactly once before any libcurl function can be used. After all usage of
complete, it \fBmust\fP call \fIcurl_global_cleanup()\fP. In between those two libcurl is complete, it \fBmust\fP call \fIcurl_global_cleanup(3)\fP. In
calls, you can use libcurl as described below. between those two calls, you can use libcurl as described below.
To transfer files, you always set up an "easy handle" using To transfer files, you always set up an "easy handle" using
\fIcurl_easy_init()\fP, but when you want the file(s) transfered you have the \fIcurl_easy_init(3)\fP, but when you want the file(s) transfered you have the
option of using the "easy" interface, or the "multi" interface. option of using the "easy" interface, or the "multi" interface.
The easy interface is a synchronous interface with which you call The easy interface is a synchronous interface with which you call
@ -60,7 +60,7 @@ get information about a performed transfer
helps building a HTTP form POST helps building a HTTP form POST
.TP .TP
.B curl_formfree() .B curl_formfree()
free a list built with curl_formparse()/curl_formadd() free a list built with \fIcurl_formadd(3)\fP
.TP .TP
.B curl_slist_append() .B curl_slist_append()
builds a linked list builds a linked list
@ -107,15 +107,15 @@ Persistent connections means that libcurl can re-use the same connection for
several transfers, if the conditions are right. several transfers, if the conditions are right.
libcurl will *always* attempt to use persistent connections. Whenever you use libcurl will *always* attempt to use persistent connections. Whenever you use
\fIcurl_easy_perform()\fP or \fIcurl_multi_perform()\fP, libcurl will attempt \fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP, libcurl will
to use an existing connection to do the transfer, and if none exists it'll attempt to use an existing connection to do the transfer, and if none exists
open a new one that will be subject for re-use on a possible following call to it'll open a new one that will be subject for re-use on a possible following
\fIcurl_easy_perform()\fP or \fIcurl_multi_perform()\fP. call to \fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP.
To allow libcurl to take full advantage of persistent connections, you should To allow libcurl to take full advantage of persistent connections, you should
do as many of your file transfers as possible using the same curl handle. When do as many of your file transfers as possible using the same curl handle. When
you call \fIcurl_easy_cleanup()\fP, all the possibly open connections held by you call \fIcurl_easy_cleanup(3)\fP, all the possibly open connections held by
libcurl will be closed and forgotten. libcurl will be closed and forgotten.
Note that the options set with \fIcurl_easy_setopt()\fP will be used in on Note that the options set with \fIcurl_easy_setopt(3)\fP will be used in on
every repeated \fIcurl_easy_perform()\fP call. every repeated \fIcurl_easy_perform(3)\fP call.