On Feb 15, 2005, at 4:42 PM, Stephen Willey wrote:
>
> Thanks for the quick response.
>
> I understand the credential caching that svn does. What's additionally
> needed is authentication state caching. Most svn user actions require
> multiple http/https requests. Without any caching of the
> authentication
> state each request has to be authenticated separately. If the authn
> backend is a networked resource then the otherwise spiffy svn request
> turns
> into molasses.
>
> Perhaps the best solution for us is to use svn+ssh://
>
I don't understand: are you actually experiencing a problem? Or are
you just predicting one? Yes, you're right that svn does multiple http
requests per action. And I can assure you that it *doesn't* re-prompt
the user for every request. :-)
Neon (http://www.webdav.org/neon) is the library the svn client uses to
send and receive all HTTP traffic. Neon has full support for openssl
and certs, and yes, it's smart enough to remember authentication
between requests. It sends a request, gets a 401 back, which causes
the svn client to prompt for authentication. Neon then remembers and
uses that authentication for every subsequent request. When the
connection to the server is finally closed, the svn client itself
(optionally) caches the authentication info in ~/.subversion/auth/, for
the next time 'svn' is invoked.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 16 01:24:06 2005