<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Summary</title>
<link rel="stylesheet" type="text/css" href="styles.css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1" />
<link rel="home" href="index.html" title="Version Control with Subversion" />
<link rel="up" href="svn.developer.html" title="Chapter 8. Embedding Subversion" />
<link rel="prev" href="svn.developer.usingapi.html" title="Using the APIs" />
<link rel="next" href="svn.ref.html" title="Chapter 9. Subversion Complete Reference" />
</head>
<body>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Summary</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="svn.developer.usingapi.html">Prev</a> </td>
<th width="60%" align="center">Chapter 8. Embedding Subversion</th>
<td width="20%" align="right"> <a accesskey="n" href="svn.ref.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" title="Summary">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="svn.developer.summary"></a>Summary</h2>
</div>
</div>
</div>
<p>One of Subversion's greatest features isn't something you
get from running its command-line client or other tools. It's
the fact that Subversion was designed modularly and provides a
stable, public API so that others—like yourself,
perhaps—can write custom software that drives Subversion's
core logic.</p>
<p>In this chapter, we took a closer look at Subversion's
architecture, examining its logical layers and describing that
public API, the very same API that Subversion's own layers use
to communicate with each other. Many developers have found
interesting uses for the Subversion API, from simple repository
hook scripts, to integrations between Subversion and some other
application, to completely different version control systems.
What unique itch will <span class="emphasis"><em>you</em></span> scratch with
it?</p>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="svn.developer.usingapi.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="svn.developer.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="svn.ref.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Using the APIs </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> Chapter 9. Subversion Complete Reference</td>
</tr>
</table>
</div>
<div xmlns="" id="svn-footer">
<hr />
<p>You are reading <em>Version Control with Subversion</em> (for Subversion 1.7), by Ben Collins-Sussman, Brian W. Fitzpatrick, and C. Michael Pilato.<br />
This work is licensed under the <a href="http://creativecommons.org/licenses/by/2.0/">Creative Commons Attribution License v2.0</a>.<br />
To submit comments, corrections, or other contributions to the text, please visit <a href="http://www.svnbook.com/">http://www.svnbook.com/</a>.</p>
</div>
</body>
</html>
distrib
>
Mageia
>
3
>
i586
>
media
>
core-updates
>
by-pkgid
>
1d6e0a3784534d5165fa22faeeca008d
>
files
>
63
