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

Re: authentication cache

From: SteveKing <steveking_at_gmx.ch>
Date: 2003-02-20 20:15:33 CET

> Heh, this isn't a bug, it's just a libsvn_auth design oversight.
I never said that :)

> Our main commandline client:
>
> creates a ctx object
> creates an auth_baton with various providers
> runs a single subcommand
> calls first_creds, next_creds, next_creds ...
> exits
As I said: it won't affect the command line client. That's why
I asked if I'd have to write my own provider for that or
if it will get into subversion itself.

> There's simply no caching design here at all, which would be needed by
> long-running GUI clients.
>
> What's happening with a GUI client is this:
>
> creates a ctx object
> creates an auth_baton with various providers
> run many subcommands
> calls first_creds, next_creds, next_creds ...
> calls first_creds, next_creds, next_creds ...
> calls first_creds, next_creds, next_creds ...
> exits
>
> I think the solution here is simple: the auth_baton can cache the last
> returned set of credentials (of each type). Then we change first_creds()
> to always return the cache, if available. Pretty easy.
Since I'm not very familiar with that code would you do it please?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 20 21:16:12 2003

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