Re: [TSVN] Re: authentication dialog fired twice

Zrubavel wrote:

> Wouldn't it be possible to reuse the credentials for the second request
> ? After all, from a user perspective, it is a single operation.

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 API svn_client_update() can takes only one path to update. But the
CL client takes multiple targets too. So if you do
svn update file1.txt file2.txt
both files are updated to HEAD individually. If now between those
updates another commit happens, you'll end up with an inconsistent
working copy. Example
HEAD = 100
updating file1.txt to HEAD = 100
another commit happens which changes file2.txt too --> HEAD = 101 now
updating file2.txt to HEAD = 101

The result is that
file1.txt has revision 100, but
file2.txt has revision 101
even though the user wanted both files to have the same revision.

TSVN however first asks the repository what the HEAD revision is and
then updates all targets to that revision. If then a commit happens in
between the individual updates, all files still are updated to the same
revision.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org