On Fri, Mar 02, 2001 at 09:48:43AM -0800, Bruce Atherton wrote:
> At 10:16 AM 02/03/2001 -0600, pohl wrote:
> >While we're on the subject of language bindings, I'd like to ask if
> >anybody here has considered how one would write a client class library
> >in Java? Would it require maintaining separate implementations in
> >Java of both Neon and libsvn_ra_dav of one didn't want to go the
> >less-portable JNI route?
> I think it depends on which libraries you are talking about.
> Regarding the FS libraries, I believe that JNI is required in order to get
> at the Berkeley DB libraries. The bindings are created as part of the
> standard build from Sleepycat. Furthermore, given the portability goals of
> Apache and Subversion, I'm not sure how much more portability a pure Java
> solution would give you.
I'd see the use of Java as a preference in this case; portability may not be
required. I know that I write much of my own stuff to always run on Linux; I
use Python primarily, but not so that it'll run on a Palm Pilot.
> If you want to avoid JNI you will need a library that talks DeltaV. For
> ease of understanding and reuse, it would probably be helpful if
> libsvn_ra_dav was reimplemented in Java as well, although there is no
> reason it would have to be. The Java client could just as easily call
> directly into the DeltaV library.
Right. Our use of WebDAV was intended to facilitate the use of standard
libraries and tools. While we will provide client-side libraries to
bootstrap peoples' code, they may still choose to "go to the metal" and use
DeltaV libraries to directly interface with the SVN server. Great for them;
it is part of our design. (no custom protocol requiring custom development)
> There are a number of projects that are developing WebDAV libraries in
> Java, such as Jakarta Slide http://jakarta.apache.org/slide/index.html,
> Websphere DAV4J http://www.alphaworks.ibm.com/aw.nsf/techmain/DAV4J, and
> WebDAV Explorer http://www.ics.uci.edu/~webdav/. Jakarta Slide even
> specifically mentions their intention to include DeltaV client support.
> None of them currently support DeltaV that I could find, though.
SkunkDAV at SourceForge is (apparently) a very good WebDAV client library.
Last I checked/heard on these: Slide is a framework, and doesn't have a
complete implementation; DAV4J has had some problems (dunno what; I should
learn more); WebDAV Explorer doesn't have a separable library. SkunkDAV is
intended to be a separable library plus a GUI app.
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:24 2006