Lines Matching full:libcurl

4 Title: libcurl
6 Source: libcurl
8   - libcurl-easy (3)
9   - libcurl-multi (3)
10   - libcurl-security (3)
11   - libcurl-thread (3)
18 libcurl - client-side URL transfers
22 This is a short overview on how to use libcurl in your C programs. There are
24 libcurl-easy(3), libcurl-multi(3), libcurl-share(3),
25 libcurl-url(3), libcurl-ws(3) and libcurl-tutorial(3) for
26 in-depth understanding on how to program with libcurl.
28 There are many bindings available that bring libcurl access to your favorite
46 the libcurl-easy(3) man page.
51 similar. The multi interface allows you to select() on libcurl action, and
53 thread. See further details in the libcurl-multi(3) man page.
62 gets detailed libcurl (and other used libraries) version info. See
85 described in the libcurl-share(3) man page.
89 URL parsing and manipulations. See libcurl-url(3)
93 See libcurl-ws(3)
95 # LINKING WITH LIBCURL
100 curl-config is added to make it easier for applications to link with libcurl
101 and developers to learn about libcurl and how to use it.
104 link with the particular version of libcurl you have installed. See the
107 Unix-like operating system that ship libcurl as part of their distributions
112 options about libraries and libcurl supports that as well.
114 # LIBCURL SYMBOL NAMES
116 All public functions in the libcurl interface are prefixed with 'curl_' (with
125 libcurl works
131 libcurl is thread safe but there are a few exceptions. Refer to
132 libcurl-thread(3) for more information.
136 Persistent connections means that libcurl can reuse the same connection for
139 libcurl always attempts to use persistent connections. Whenever you use
140 curl_easy_perform(3) or curl_multi_perform(3) etc, libcurl
145 To allow libcurl to take full advantage of persistent connections, you should
149 the possibly open connections held by libcurl are closed and forgotten.
158 There are a variety of constants that libcurl uses, mainly through its
162 the library code. For example, when libcurl is built for SSL
170 If libcurl was compiled with support for multiple SSL backends, the function
174 The global constant functions are thread-safe since libcurl 7.84.0 if
176 (most platforms). Read libcurl-thread(3) for thread safety guidelines.
180 is not good enough that no other thread is using libcurl at the time,
187 for constructing a program that uses libcurl is this: Call
190 libcurl at all. Call curl_global_cleanup(3) immediately before the
192 use of libcurl.
201 are writing to use libcurl is not the main program, but rather a modular piece
203 other parts of the program -- it does not know whether they use libcurl or
210 the libcurl functions. If multiple modules in the program use libcurl, they
211 all separately call the libcurl functions, and that is OK because only the
213 program change anything. (libcurl uses a reference count in static memory).
220 author of this libcurl-using module, you can make the constructor call
222 and satisfy libcurl's requirements without your user having to think about it.
223 (Caveat: If you are initializing libcurl from a Windows DLL you should not
230 must have specific knowledge of internal workings of libcurl and all other
237 modular program -- all modules in the program that might use libcurl would
240 There is a failsafe in libcurl that makes it usable in simple situations