summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2004-03-15 12:41:24 +0000
committerDaniel Stenberg <daniel@haxx.se>2004-03-15 12:41:24 +0000
commit7de892eeb4203e5a41b8943cd108e7c4d1e02883 (patch)
tree654189fb02f4bad9ecb99ed32e2763c88c746666 /docs
parent8c4e91a653de78deab7bd2a6f8a3c6197dc7730d (diff)
downloadcurl-7de892eeb4203e5a41b8943cd108e7c4d1e02883.tar.gz
more formatting fixes
Diffstat (limited to 'docs')
-rw-r--r--docs/libcurl/libcurl.319
1 files changed, 9 insertions, 10 deletions
diff --git a/docs/libcurl/libcurl.3 b/docs/libcurl/libcurl.3
index 422d56f29..54c7d0a54 100644
--- a/docs/libcurl/libcurl.3
+++ b/docs/libcurl/libcurl.3
@@ -8,8 +8,8 @@ libcurl \- client-side URL transfers
.SH DESCRIPTION
This is an overview on how to use libcurl in your C programs. There are
specific man pages for each function mentioned in here. There are also the
-\fIlibcurl-easy\fP man page, the \fIlibcurl-multi\fP man page, the
-\fIlibcurl-share\fP man page and the \fIlibcurl-the-guide\fP document for
+\fIlibcurl-easy(3)\fP man page, the \fIlibcurl-multi(3)\fP man page, the
+\fIlibcurl-share(3)\fP man page and the \fIlibcurl-the-guide\fP document for
further reading on how to do programming with libcurl.
There exist more than a dozen custom bindings that bring libcurl access to
@@ -25,10 +25,9 @@ To transfer files, you always set up an "easy handle" using
option of using the "easy" interface, or the "multi" interface.
The easy interface is a synchronous interface with which you call
-\fIcurl_easy_perform\fP and let it perform the transfer. When it is completed,
-the function return and you can continue. More details are found in the
-.BR "libcurl-easy (3)"
-man page.
+\fIcurl_easy_perform(3)\fP and let it perform the transfer. When it is
+completed, the function return and you can continue. More details are found in
+the \fIlibcurl-easy(3)\fP man page.
The multi interface on the other hand is an asynchronous interface, that you
call and that performs only a little piece of the tranfer on each invoke. It
@@ -38,7 +37,7 @@ even to easily download multiple files simultaneously using a single thread.
You can have multiple easy handles share certain data, even if they are used
in different threads. This magic is setup using the share interface, as
-described in the \fIlibcurl-share\fP man page.
+described in the \fIlibcurl-share(3)\fP man page.
There is also a series of other helpful functions to use. They are:
@@ -102,12 +101,12 @@ Never ever call curl-functions simultaneously using the same handle from
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
more than one thread simultaneously.
-.SH "PERSISTANT CONNECTIONS"
+.SH "PERSISTENT CONNECTIONS"
Persistent connections means that libcurl can re-use the same connection for
several transfers, if the conditions are right.
-libcurl will *always* attempt to use persistent connections. Whenever you use
-\fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP, libcurl will
+libcurl will \fBalways\fP attempt to use persistent connections. Whenever you
+use \fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP, 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 for re-use on a possible following
call to \fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP.