[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: DAV is complicated and slow? (was Re: [svndiff1] Accept-Encoding in mod_dav_svn)

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-11-22 15:07:47 CET

Ben Collins-Sussman <sussman@red-bean.com> writes:

> Let me clarify something here:
>
> I'm definitely *against* removing all DAV support in both client and
> server. It sounds like this conversation is moving in that
> direction. The reason I'm against such a move is because I think
> that we get real value from having a DAV-compatible server, not just
> "one which speaks HTTP"
>
> - the ability to web-browse HEAD without any CGI installed
> - the ability to mount repositories from almost any OS
> - autoversioning

So far you've listed reasons not to remove DAV support in the server
(which, by the way, no one has suggested). You've provided no reasons
for leaving the use of the server's DAV support in the client (which,
by the way, I daresay nobody wants). Regardless, I'm not sure why you
thought the conversation was moving towards full removal of DAV
support. You pretty much said the same thing I did, and no respondee
has said otherwise.

The chatter has been about making Subversion *clients* stop talking
DAV to the server, but talk something else. (I dunno, maybe that
implies we have a new mod_svn module ... that'd be cool.) But nobody
is talking about removing the parts of the DAV server functionality
that we like (the stuff that gives us autoversioning, browseable HEAD
URLs, mountabled repositories, etc.).

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 22 15:14:05 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.