[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: <striker_at_apache.org>
Date: 2003-01-24 19:12:19 CET

 From: sussman@collab.net [mailto:sussman@collab.net]
 Sent: Friday, January 24, 2003 7:04 PM

 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.


We just need a function to dup the baton, so we can get to it later.
Reason for this is that the current pool we are using might get cleared/
destroyed, while we may want to retain the iteration baton (by storing
it in a long lived pool). Use case: GUI client.


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:40 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.