mirror of
https://github.com/moparisthebest/curl
synced 2024-12-22 08:08:50 -05:00
spell checked and removed talk about very old version numbers
This commit is contained in:
parent
2a72641a0b
commit
14d1da3ae0
@ -2,7 +2,7 @@
|
|||||||
.\" nroff -man [file]
|
.\" nroff -man [file]
|
||||||
.\" $Id$
|
.\" $Id$
|
||||||
.\"
|
.\"
|
||||||
.TH libcurl 5 "19 March 2002" "libcurl 7.8.1" "libcurl overview"
|
.TH libcurl 3 "19 March 2002" "libcurl 7.9.6" "libcurl overview"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
libcurl \- client-side URL transfers
|
libcurl \- client-side URL transfers
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
@ -21,7 +21,8 @@ calls, you can use libcurl as described below.
|
|||||||
|
|
||||||
When using libcurl's "easy" interface you init your session and get a handle,
|
When using libcurl's "easy" interface you init your session and get a handle,
|
||||||
which you use as input to the easy interface functions you use. Use
|
which you use as input to the easy interface functions you use. Use
|
||||||
\fIcurl_easy_init()\fP to get the handle.
|
\fIcurl_easy_init()\fP to get the handle. There is also the so called "multi"
|
||||||
|
interface, try the \fIlibcurl-multi(3)\fP man page for an overview of that.
|
||||||
|
|
||||||
You continue by setting all the options you want in the upcoming transfer,
|
You continue by setting all the options you want in the upcoming transfer,
|
||||||
most important among them is the URL itself (you can't transfer anything
|
most important among them is the URL itself (you can't transfer anything
|
||||||
@ -75,9 +76,8 @@ portable case insensitive string comparisons
|
|||||||
.RE
|
.RE
|
||||||
|
|
||||||
.SH "LINKING WITH LIBCURL"
|
.SH "LINKING WITH LIBCURL"
|
||||||
Starting with 7.7.2 (on unix-like machines), there's a tool named curl-config
|
On unix-like machines, there's a tool named curl-config that gets installed
|
||||||
that gets installed with the rest of the curl stuff when 'make install' is
|
with the rest of the curl stuff when 'make install' is performed.
|
||||||
performed.
|
|
||||||
|
|
||||||
curl-config is added to make it easier for applications to link with libcurl
|
curl-config is added to make it easier for applications to link with libcurl
|
||||||
and developers to learn about libcurl and how to use it.
|
and developers to learn about libcurl and how to use it.
|
||||||
@ -103,19 +103,18 @@ several threads. libcurl is thread-safe and can be used in any number of
|
|||||||
threads, but you must use separate curl handles if you want to use libcurl in
|
threads, but you must use separate curl handles if you want to use libcurl in
|
||||||
more than one thread simultaneously.
|
more than one thread simultaneously.
|
||||||
.SH "PERSISTANT CONNECTIONS"
|
.SH "PERSISTANT CONNECTIONS"
|
||||||
With libcurl 7.7, persistant connections were added. Persistant connections
|
Persistent connections means that libcurl can re-use the same connection for
|
||||||
means that libcurl can re-use the same connection for several transfers, if
|
several transfers, if the conditions are right.
|
||||||
the conditions are right.
|
|
||||||
|
|
||||||
libcurl will *always* attempt to use persistant connections. Whenever you use
|
libcurl will *always* attempt to use persistent connections. Whenever you use
|
||||||
curl_easy_perform(), libcurl will attempt to use an existing connection to do
|
curl_easy_perform(), libcurl will attempt to use an existing connection to do
|
||||||
the transfer, and if none exists it'll open a new one that will be subject
|
the transfer, and if none exists it'll open a new one that will be subject for
|
||||||
for re-use on a possible following call to curl_easy_perform().
|
re-use on a possible following call to curl_easy_perform().
|
||||||
|
|
||||||
To allow libcurl to take full advantage of persistant 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
|
do as many of your file transfers as possible using the same curl handle. When
|
||||||
handle. When you call curl_easy_cleanup(), all the possibly open connections
|
you call curl_easy_cleanup(), all the possibly open connections held by
|
||||||
held by libcurl will be closed and forgotten.
|
libcurl will be closed and forgotten.
|
||||||
|
|
||||||
Note that the options set with curl_easy_setopt() will be used in on every
|
Note that the options set with curl_easy_setopt() will be used in on every
|
||||||
repeat curl_easy_perform() call
|
repeat curl_easy_perform() call
|
||||||
|
Loading…
Reference in New Issue
Block a user