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

Re: Feature Request: Allow "save authentication" for reading and writing separately

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-09-06 18:00:13 CEST

Ron Wilson wrote:
> as I understand Mr Gough request, I think what he is asking for is
> that when simply querying the respository, that the read
> authentication, once performed, be remembered for future queries.
> However, when an Update is requested, the authentication be forced,
> even if a valid authentication has been remembered. this could be
> accomplished by having Update "forget" the authentication before
> taking any action. This would help protect against accidental Updates.

The problem here is that TSVN doesn't know beforehand whether a command
does a write or simply reads. Yes, most of the time that's known, but
there are some edge cases.

> Likewise, if doing a "piece-wise" Commit, say from the "Check for
> Modification" window, then the write authentication would be
> remembered until the window is closed, at wich point the
> authentication would be "forgotten".
> Otherwise, if I read his original message correctly, each individual
> query or commit from such a window would pop up the authentication
> box.

As I said, this could be done by configuring the server to use two
different users (or even two different passwords): one for read and one
for writes.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Sep 6 17:57:22 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.