forked from curl/curl-www
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path_features.html
158 lines (132 loc) · 5.59 KB
/
_features.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
#include "_doctype.html"
<html>
<head> <title>libcurl - What Makes It Special</title>
#include "css.t"
</head>
#define LIBCURL_FEATURES
#define CURL_URL libcurl/features.html
#include "setup.t"
#include "_menu.html"
WHERE2(libcurl, "/libcurl/", What Makes It Special)
TITLE(libcurl - What Makes It Special)
<div class="relatedbox">
<b>Related:</b>
<br><a href="/docs/copyright.html">License</a>
</div>
<a name="reliable"></a>
SUBTITLE(Solid and Reliable!)
<p>
libcurl was released in its current "incarnation" in the year 2000 and it has
been in constant use by a large number of applications
and <a href="/docs/companies.html">companies</a> ever since. Sure there have
been bugs and even a few <a href="/docs/security.html">security-related</a>
flaws, but it has remained a very solid and reliable library and lots of
users are still using libcurl versions released many years ago as they stick
with what works.
<a name="widelyused"></a>
SUBTITLE(Widely Used!)
<p>
libcurl is the most used C-based highly portable transfer library in the
world. Some of the world's
biggest <a href="/docs/companies.html">companies</a> use libcurl in high
volume applications. Some of the open source applications using libcurl are
very widely used.
<p>
We estimate that every internet connected human on the globe uses (lib)curl,
knowingly or not, every day.
<a name="portable"></a>
SUBTITLE(Portable!)
<p>
libcurl has been ported to numerous platforms and CPUs. libcurl offers the
same API and feature set on all of them! Using libcurl assures you that you
can write your application to work on very large amount of systems, including
but not limited to Solaris, NetBSD, FreeBSD, OpenBSD, Darwin, HPUX, IRIX,
AIX, Tru64, Linux, UnixWare, HURD, Windows, Amiga, OS/2, BeOs, Mac OS X,
Ultrix, QNX, OpenVMS, RISC OS, Novell NetWare, DOS and more...
<a name="thread"></a>
SUBTITLE(Thread Safe!)
<p>
libcurl is thread safe but there are a few exceptions. Refer to <a
href="//curl.se/libcurl/c/libcurl-thread.html">libcurl-thread(3)</a>
for more information.
<a name="features"></a>
SUBTITLE(Unmatched Set of Features!)
<p>
There simply is no other HTTP and FTP library that can boast the same amount
and set of <a href="/docs/features.html">features</a> that libcurl does. Be
it free or commercial.
<p>
Also, libcurl's unique offer of both a pull and push interface allows
applications to use it exactly the way they please.
<p>
libcurl also offers an unmatched set of bindings, enabling you to access and
use libcurl from basically whatever language you can think of!
<a name="ipv6"></a>
SUBTITLE(Supports IPv6!)
<p>
If compiled with IPv6 support enabled, <b>All protocols</b> work splendidly
on IPv6 stacks. There are some minor quirks to keep in mind: kerberos4 does
not work over IPv6 by design and the SOCKS4 support is not properly adapted
for IPv6.
<p> There is nothing in particular needed to get IPv6 to be used, the library
API remains exactly the same and adjusts to IPv4/IPv6 dynamically. You can
use host names that only have AAAA DNS records, or you can use IPv6 IP-only
style addresses like <tt>[::1]</tt>.
<a name="support"></a>
SUBTITLE(Well Supported!)
<p>
We claim libcurl is well supported because you can get help on one of the
mailing lists, very quickly and accurately. Often within a few hours. Having
the mailing list archives available on the web also makes them searchable and
allows you to find already mentioned solutions and answers.
<p>
We have a public bug tracker and known bugs are mostly fixed very swiftly.
<p>
We also provide very detailed documentation on all operations, not just in
every release archive but also available on the web site(s).
<p>
You can get paid support from one of the listed <a href="/support.html">curl
support</a> companies.
<p>
Since the code is free and available, any skilled programmer can fix and
improve the tool and library whenever. If you can't, you can hire one!
<a name="fast"></a>
SUBTITLE(Fast!)
<p>
Tests performed by independent users, have repeatedly proved libcurl to be
fast.
<p>
When using libcurl bindings, you will get unmatched speeds due to libcurl
being programmed in C and very often the language-specific alternatives (be
it perl, Python, PHP, tcl or whatever) are <i>much</i> slower.
<a name="docs"></a>
SUBTITLE(Thoroughly Documented!)
<p> All functions in libcurl have their own detailed <a
href="/libcurl/c/allfuncs.html">man pages</a> describing their actual
functionality and purpose.
<p> All interfaces have overview-style man pages describing the concepts that
glue all the functions together: <a
href="/libcurl/c/libcurl-easy.html">easy</a>, <a
href="/libcurl/c/libcurl-multi.html">multi</a>, <a
href="/libcurl/c/libcurl-share.html">share</a> and <a
href="/libcurl/c/libcurl-url.html">URL parsing</a>.
<p> There is a <a href="/libcurl/c/libcurl-tutorial.html">libcurl tutorial</a>.
<p> We have numerous commented <a href="/libcurl/c/example.html">source code
examples</a>.
<a name="stableapi"></a>
SUBTITLE(Stable API and ABI)
<p>
In the libcurl development we take API and ABI stability <b>very
seriously</b>. We have a few rules when it comes to API and ABI compatibility
and they are:<ol>
<li> We don't break API or ABI compatibility
<li> Seriously, we really don't and we work very hard to provide alternatives
that introduce new ways instead of breaking old
<li> A few times in the beginning of our project we felt forced to break
existing behavior and we did API and ABI bumps. It was painful and hard and
bad and we <b>really really</b> don't want to do it again. Ever! We have not
done it since 2006.
</ol>
#include "_footer.html"
</body>
</html>