| 1 |
<sect1 id="features"> |
| 2 |
<title>Feature list</title> |
| 3 |
|
| 4 |
<para>The major features of the neon library are as follows:</para> |
| 5 |
|
| 6 |
<itemizedlist> |
| 7 |
|
| 8 |
<listitem><para>A high-level interface to common HTTP and WebDAV |
| 9 |
methods. This allows you to easily dispatch a GET or a MKCOL request |
| 10 |
against a resource with a single function call.</para></listitem> |
| 11 |
|
| 12 |
<listitem><para>A low-level interface for HTTP request |
| 13 |
handling; allowing you to implement requests using arbitrary methods |
| 14 |
and request headers, capture arbitrary response headers, and so |
| 15 |
on.</para></listitem> |
| 16 |
|
| 17 |
<listitem><para>Persistent connection support; neon groups a |
| 18 |
set of requests to a server into a "session"; requests within that |
| 19 |
session can use a persistent (also known as "keep-alive") |
| 20 |
connection.</para></listitem> |
| 21 |
|
| 22 |
<listitem><para>Modern HTTP authentication support: a complete |
| 23 |
implementation of the new authentication standard, RFC2617, supporting |
| 24 |
the Digest, Basic, and Negotiate protocols. Credentials are supplied |
| 25 |
by an application-defined callback as appropriate.</para></listitem> |
| 26 |
|
| 27 |
<listitem><para>Proxy server support; a session can be set to |
| 28 |
use a proxy server. Authentication is supported for the Proxy as well |
| 29 |
as the origin server. The system's proxy configuration can be |
| 30 |
optionally used, on some platforms.</para></listitem> |
| 31 |
|
| 32 |
<listitem><para>Complete SSL support; a simple interface for |
| 33 |
enabling SSL, hiding the complexity of using an SSL library directly. |
| 34 |
Client certificate support, callback-based server certificate |
| 35 |
verification, along with functions to load trusted CA certificates. |
| 36 |
Smartcard-based client certs are also supported via a wrapper |
| 37 |
interface for PKCS#11 modules.</para></listitem> |
| 38 |
|
| 39 |
<listitem><para>Compressed response support: responses |
| 40 |
compressed using the "deflate" algorithm can be transparently |
| 41 |
decompressed.</para></listitem> |
| 42 |
|
| 43 |
<listitem><para>Generic XML parsing interface for handling XML |
| 44 |
response bodies using SAX-like callbacks. Both the expat and libxml |
| 45 |
XML parser libraries are supported.</para></listitem> |
| 46 |
|
| 47 |
<listitem><para>WebDAV metadata support; set and remove |
| 48 |
properties, query properties (PROPFIND); simple interface for |
| 49 |
retrieving "flat" byte-string properties, more advanced support for |
| 50 |
parsing "complex" structured XML properties.</para></listitem> |
| 51 |
|
| 52 |
<!-- |
| 53 |
<listitem><para>WebDAV locking support</para></listitem> |
| 54 |
--> |
| 55 |
|
| 56 |
<listitem><para>Build environment support: the neon source |
| 57 |
tree is designed so that it can be embedded in your application's |
| 58 |
build tree; autoconf macros are supplied for integration. To get |
| 59 |
started quickly a <xref linkend="refconfig"/> script is included, |
| 60 |
to easily determine how to compile and link against an installed copy |
| 61 |
of neon</para></listitem> |
| 62 |
|
| 63 |
<listitem><para>Complete test suite: the neon test suite |
| 64 |
comprises half as many lines of source code as the library itself, |
| 65 |
including many tests for protocol compliance in network behaviour, and |
| 66 |
that the library implementation meets the guarantees made by the |
| 67 |
API.</para> </listitem> |
| 68 |
|
| 69 |
<!-- |
| 70 |
|
| 71 |
<listitem><para>Thorough documentation: neon documentation is |
| 72 |
provided in HTML and man page formats (from a single DocBook XML |
| 73 |
source)</para></listitem> |
| 74 |
|
| 75 |
--> |
| 76 |
|
| 77 |
</itemizedlist> |
| 78 |
|
| 79 |
</sect1> |