
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
Using the APIs
|
173
opens an authenticated session with a particular repository. It then asks the reposi-
tory for a certain tree, and sends this tree into the working copy library, which then
writes a full working copy to disk (.svn directories and all).
The client library is designed to be used by any application. While the Subversion
source code includes a standard command-line client, it should be very easy to write
any number of GUI clients on top of the client library. New GUIs (or any new client,
really) for Subversion need not be clunky wrappers around the included command-
line client—they have full access via the libsvn_client API to same functionality,
data, and callback mechanisms that the command-line client uses.
Using the APIs
Developing applications against the Subversion library APIs is fairly straightforward.
All of the public header files live in the subversion/include directory of the source tree.
These headers are copied into your system locations when you build and install Sub-
version itself from source. These headers represent the entirety of the functions and
types meant to be accessible by users of the Subversion libraries.
The first thing you might notice is that Subversion’s datatypes and functions are
namespace protected. Every public Subversion symbol name ...