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

RE: [PATCH] default to --no-auth-cache

From: Sander Striker <striker_at_apache.org>
Date: 2003-01-14 22:37:37 CET

> From: rbb@rkbloom.net [mailto:rbb@rkbloom.net]
> Sent: Tuesday, January 14, 2003 10:48 PM

[...]
>> Well, then why don't we go for that immediately? Drop all this
>> auth-cache vs. no-auth-cache thing, and write svn-agent daemon. Then we
>> truly don't have to keep anything on disk. Of course, it does make
>> client configuration a bit harder, but hey.
>
> Because you still need the auth-cache stuff. :-) For the most common
> case for subversion, you will have people setting up subversion for public
> consumption, which means that not everybody will be able to use
> client-side certs for authentication. It also means that not all
> subversion servers will be run over SSL.

You're missing the point. Use svn-agent for all auth info, regardless
whether you are doing basic auth or you need a pass for your cert.
 
> Yeah, client side config is even harder, because there are a lot of
> options, but I can't find a way to get rid of any of them.

Actually, I think it becomes easier... No svn-agent == no caching.
And a running svn-agent == caching. Now svn-agent could have config
options like expiry of cache etc, but hey... ;) :)

Sander

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 14 22:38:20 2003

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.