Re: architecture questions

I'm fairly new to the project, so take my observations with a grain of salt.

On Tuesday 09 December 2003 02:56 pm, Ben Collins-Sussman wrote:
> First:  do I understand the architecture correctly?
>
>    * svnjavahl.dll contains all of the libsvn_*.dll libraries.

not sure about windows, but on linux, svnjavahl dynamically links in with the
rest of the libsvn_*, they are not compiled in.

>
>    * javahl.jar talks to svnjavahl.dll via JNI.

yup. javahl define

>    * javahl.jar has an SvnClient.class, but the whole
>      SvnClientAdapter.jar is a replacement API for that class.

svnclient was at some point deemed too hard to use. jni interfaces are often
not oo, or at best not written in a way fitting into the java programming
idiom (which is quite different from c or c++).

>    * SVNPluginCore.jar is the actual Eclipse plugin, and depends on
>      SvnClientAdapter.jar.

yup. as is the "ui" project.

> If so, then
>
>    * since there's already a JNI dependency, why does
>      SvnClientAdapter.jar have a set of classes just for wrapping the
>      svn cmdline client?  Why is the svn cmdline client used at all?

I'm a bit fuzzy on why this exists too. Someone probably asked for it. My
guess is that building libsvnjavahl has been historically quite involved
compared to building the commandline clients (it's not build from the
toplevel svn build, nor is it included in binary releases), and some users
want to just use what they already have.

>    * I've scoured through the binary .zip distribution, and I can't
>      find the svn cmdline client anywhere.  Yet I see the cmdline
>      client running in a window when I do a checkout.  Where is it??

the console windows prints out the commandline that would be used if you were
in commandline operation mode. The default operational mode is jni.

-- 
McClain Looney
LoonSoft LLC
m@loonsoft.com