SteveKing wrote:
> It's possible, yes. But not without rewriting a lot of the Subversion
> library or duplicating it in TSVN. You see, Subversion offers some
> functions like svn_client_update(), but those functions don't expose the
> credential caching so there's not an easy way to reuse them.
> But why don't you save your authentication data? I mean if you're not
> using Win98 or NT4 those authentication data is stored encrypted so no
> one else but you can ever use it! (And even you would have a hard time
> decrypting it).
The use case we have involves a computer shared by a number of
developers, because of the custom hardware installed. Since we want the
commits from this machine to be properly attributed, we can't save
authentication data. (yes, the data can be cleared and re-entered before
the commit, but remembering to do this turned out tricky :)
One possible implementation path would be caching authentication
regardless of the checkbox value, and clearing it when the update
completes. That would mean adding the ability to selectively remove
stored credentials that are marked 'for current operation only'.
Or maybe an alternative in-memory cache ? Haven't looked at the source
yet, so i don't know how complicated these ideas might be to implement.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Dec 4 15:09:53 2004