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

Re: username/password caching

From: <cmpilato_at_collab.net>
Date: 2003-02-22 16:47:59 CET

Ben Collins-Sussman <sussman@collab.net> writes:

> cmpilato@collab.net writes:
>
> > Then I thought, what if each provider's "save" function accepted a
> > flag that dictated the amount of data to save:
> >
> > 'none' - store no creds (but the system would call the function
> > anyway in case the provider needs to do some kind of cleanup or
> > admin task).
> >
> > 'username' - store a username only.
> >
> > 'all' - store all the creds.
> >
> > Then, we would change the config option to "auth-cache-type" (and the
> > valid values would be 'none', 'username', or 'all', defaulting to
> > 'username') and then change the command-line argument to
> > "--auth-cache-type" with the same three valid values.
>
> +1 on this idea, provided it's not a flag to every single save_creds()
> implementation. Instead, it should be a simple runtime parameter in
> the auth_baton hash. It can either be specific to the wc provider, or
> global to all providers that might want to care.

Ah yes, the hash. Forgot about that. +1!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 22 18:49:41 2003

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