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

Re: Semantics of svn_auth_save_credentials?

From: <sussman_at_collab.net>
Date: 2003-01-24 19:04:17 CET

Sander Striker striker@apache.org writes:

  Now, you could say that because the user placed the 'file' provider
  first that that is their 'preferred' provider. But, I'm not sure
  that's exactly what we would want. Is it? -- justin
 It is likely that we wish to update creds in the provider we got them
 from. We would need to save the provider and the old creds and pass
 those optionally to the save function. This should then first
 try the passed in provider and see if it can update the old creds.
 If not, it should start at the first provider and cycle through them
 until it finds one that wishes to store the new creds (or it doesn't
 find one ofcourse).

This makes sense to me. All we have to do is make the public
svn_auth_save_creds() function take the iteration baton that was
already being used by svn_auth_first_creds() and
svn_auth_next_creds(). The iteration baton *already* remembers which
provider was last called.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:14:31 2006

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.