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

Re: svn commit: r1572105 - in /subversion/trunk/subversion: svn/auth-cmd.c svn/cl.h svn/svn.c tests/cmdline/getopt_tests_data/svn--help_stdout tests/cmdline/getopt_tests_data/svn_help_stdout

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 27 Feb 2014 14:06:38 +0100

On Thu, Feb 27, 2014 at 04:53:18PM +0400, Ivan Zhakov wrote:
> Names used in internal API is not important for me.

I think it's important to have some consistency in the naming schemes
used for internal and externals interfaces. The APIs are public APIs
which we provide to our users just like we provide the command line

We also currently expect users to remove cached credentials from the
'.subversion/auth' directory, so the term 'auth' is already familiar:
I've never seen users being confused by this terminology.

> I worry about
> possible user confusion that 'svn auth' subcommand is
> responsible/required to perform authentication itself.

Yes, I see that problem, too. This is why I thought about alternatives
such as 'svn authcreds', 'svn authinfo', 'svn authcache'. I don't see
a clear advantage of using 'svn creds' instead of any of the other names.

Also note that the help text mentions 'credentials' for this reason:
auth: Manage cached authentication credentials.
Received on 2014-02-27 14:07:35 CET

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.