Subversion's interfaces are cleaner than that:
CLIENT LAYER (two entry points):
libsvn_client --> libsvn_wc
--> RA LAYER
libsvn_wc
RA LAYER (single exposed entry point with four virtual providers):
libsvn_ra --> libsvn_ra_svn -(net)-> svnserve --> REPOS LAYER
--> libsvn_ra_local --> REPOS LAYER
--> libsvn_ra_neon -(net)-> mod_dav_svn --> REPOS LAYER
--> libsvn_ra_serf -(net)-> mod_dav_svn --> REPOS LAYER
REPOS LAYER (two entry points):
libsvn_repos --> libsvn_fs
libsvn_fs
See attached quickly-and-not-clealy revised diagram.
Jeroen Bach wrote:
> Hello,
>
> For an assignement at the university we have to design an architectural
> change to subversion, implementing a new feature.
> But we got a little stuck on the repository access and the server
> hosting the repository. We want to have a understanding on which files
> (group of functions) calls which other files.
>
> What we found was the following: (each arrow is a call, the packages are
> directory's and the blocks in the package are files)
>
>
>
> ------------------------------------------------------------------------
>
>
>
>
> Somewhere a call goes through the internet and comes in svnserve or
> Apache. Then we got a little lost, which files and packages (folders)
> are called next? where is the libsvn_repos called?
> can someone enlighten us?
>
> Your help will be very appreciated.
>
> Thanks in advanced,
>
> Jeroen Bach
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2008-09-23 17:17:44 CEST