Nathan Kidd wrote:
> Add a checkbox to the Commit dialog
> "Ask for Authentication Credentials"
> When checked, the commit dialog would pop up the "Authentication" dialog
> regardless of whether saved authentication data exists for this repo or not.
How would you find out *which* saved auth data to delete? Subversion
stores them under a folder with the name being an md5 hash of the
repository root (*not* the URL, not the domain, but the repository
root). Now that repository root is *not* known prior to connecting to
the repository (which also requires authentication).
Deleting *all* stored authentication instead? *no*! People will start
complaining a lot, and with good reason.
Just not using the auth cache provider? Maybe. But then, auth data also
can't be stored, so the auth dialog would have to be modified to *not*
show the "save authentication data" checkbox. Also, that would mean that
there's not auth caching during the whole session, which means you'll be
asked for authentication multiple times. And the next time you don't
check the "ask for auth" checkbox as you suggest, the 'old'
authentication data will be used again, not the last one you've entered
while having that checkbox enabled.
That will confuse people much more than the current behaviour.
> 1) developer A working with developer B at developer B's desk. Changes
> are really from developer A, and should be committed as such, but
> developer B's auth data is already saved. They are forced to either
> clear the auth cache in tsvn settings (annoying for developer B
> afterward) or temporarily rename the saved auth file for this repo UUID
> (also annoying and time consuming).
But if you clear the auth cache, developer B will at least know that
someone else was using his computer again (maybe that's why you don't
want to do that - because you know that he will be mad at you?)
> 2) a "build" user normally checks out/updates code on build machine, but
> regularly we find ourselves debugging or tweaking build issues on the
> build machine and then needing to commit. Using --no-auth-cache in all
> scripts doesn't help because we frequently need to see file history and
> don't want to enter auth creds every time Show Log loads. Even if we
> used consistent --no-auth-cache (in cmd line client) and
> 'store-auth-creds = no' in the config file, javahl seems to ignore
> store-auth-creds anyway.
Then you should report this on the Subversion mailing list. In that
case, javahl has a bug and should be fixed.
> 3) machine is occasionally used by two people via terminal services
> Attached is a screenshot of how it might look.
Even if you might argue that 'it's only one simple checkbox', I still
think it clutters the UI - for something maybe 1% of all people will
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Sep 18 18:23:26 2005