[Took it back on the list]
Erik Huelsmann wrote:
> On Thu, Jun 25, 2009 at 10:28 AM, John Beranek<john_at_redux.org.uk> wrote:
>> Hyrum K. Wright wrote:
>>> On Jun 24, 2009, at 10:05 AM, John Beranek wrote:
>>>> That wouldn't help though - commits from India direct to the UK master
>>>> are still _very_ slow.
>>> Subversion's HTTPv2, a reduced-turnaround implementation of the DAV
>>> protocol will debut in Subversion 1.7. It doesn't help you *now*, but
>>> hopefully it will have significant impact on high-latency links, such as
>>> from India to the UK. You can read about it here:
>> Well, it's good to know development effort is being spent on improving
>> HTTP Subversion access, especially as it seems that svn:// access is
>> very much downplayed (and not developed?).
> I'm sorry? Where did you get that impression? Downplayed? The
> developers agree that it's the fastest way to communicate with a
> Subversion server. It has been extended with a pluggable SASL library
> for extended authentication possibilities.
Hmm, just reread chapter 6 of the SVN book and I guess it's not exactly
downplayed, but it does miss out on a few features:
* An easy to fathom pluggable authentication layer - SASL just blows my
* Transparent proxying for mirror servers, this would be quite a win.
* No logging of access at all - though I can't get especially excited
about this, if I'm honest.
> By nature of it not being HTTP, ofcourse it's not proxy-able through
> HTTP proxies, although I've read some articles on the web to proxy
> anything though an HTTP proxy using the CONNECT method.
Proxying through the Internet isn't of interest to me as a commercial
user, apart from the local read/remote write functionality that you can
get for replication for Subversion over HTTP.
John Beranek To generalise is to be an idiot.
http://redux.org.uk/ -- William Blake
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-25 11:01:48 CEST