On Thu, 22 Mar 2007, Blair Zajac wrote:
> I may end up doing some of these myself, but I'd like to put them out
> there for discussion.
> 1) Have an embeddable svnserve. Today, I was writing a Java servlet
> that forked a svnserve process. The Java servlet exposes a ICE (CORBA
> like) API for remote clients. The servlet uses the Subversion
> filesystem under the hood to have a versioned database, but the clients
> of the servlet don't know that. They see a very-non Subversion like API.
> Instead of dealing with the issues of starting and stopping a child
> process in Java, it would be cool to abstract out the code in svnserve
> so that anybody could embed svnserve protocol svn server in their own code.
> No telling where svnserve's may start showing up if they are very easy
> to embed and make a Subversion repository networkable
> 3) Come up with a common Subversion objected oriented abstraction for
> all bindings. I think we spoke about this at the summit. Comments were
> made that the Ruby bindings were the best designed.
> Instead of having each binding have thier own OO feel, they all
> implement the same feel.
> This isn't too codey, and may not make a good SOC project.
#3 should definitely be listed. We talked about this at the last
Subversion Summit in Mountain View.
> Let me know if these would be appropriate and I can put them up in the
> project_tasks.html page.
Received on Tue Mar 27 03:01:56 2007
- application/pgp-signature attachment: stored