On Sun, Nov 9, 2008 at 2:22 PM, Blair Zajac <blair_at_orcaware.com> wrote:
>...
> I see two ways to do this.
>
> One, write a HTTP protocol that mirrors the RA API. This puts most of the
> coding work in mod_dav_something to map RA down to svn_fs.h.
>
> Two, write a HTTP protocol that mirrors svn_fs.h and svn_repos.h. Then the
> mod_dav_something layer is very straight forward and the client side RA code
> needs to do more of the work mapping RA down to basic calls.
The network is a limited resource, so the ideal mapping will match
what the client needs. That gets transported over the wire, and then
the server figures it out. If the client needs an extra round trip
because of impedance with the server API, then you've lost.
In any case... I think we're off on a tangent here. Ben is going to
modify ra_serf and mod_dav_svn. Nobody else has signed up to do any
network code, so until that happens... what are we discussing? :-P
Cheers,
-g
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-09 23:31:27 CET