On Wed, Oct 1, 2008 at 6:13 PM, Ben Collins-Sussman
<sussman_at_red-bean.com> wrote:
> 2008/10/1 Bert Huijben <B.Huijben_at_competence.biz>:
>
>
>> I think providing both mod_dav_svn and mod_svn over the same public url encourages users to upgrade their servers to support mod_svn, while requiring all users to upgrade their clients before the migration will hold the server upgrade until the adminstrators are sure all users have updated.
>> Which might take a couple of years for big hosters like sourceforge.
>
> I agree this would be ideal, but it's not technically possible. As I
> said before, two modules cannot both "own" the same public url. If
> you have a brilliant idea on how to implement this, I'm all ears.
Two apache modules could easy handle the same public url. You just to
register handler hook before mod_dav_svn and then return DECLINED if
url is not accepted. For example if it doesn't have cmd=something in
args. And return OK in other cases. mod_svn_view module uses this
approach for implementing Subversion web interface on the same URLs as
Subversion.
--
Ivan Zhakov
VisualSVN Team
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-01 17:08:23 CEST