Hi Karl,
thanks for summing it up
> (I know this
> insistence on an issue might seem like reflexive bureaucracy, but I
> find it makes it much easier to understand & solve the problem.)
I agree with you. It's much better to remove the cause and the symptom ;-)
> Your mail is the closest we've gotten to a summary so far; let me try
> to boil it down further:
>
> 1) Right now, failing to get the username from the system is a
> fatal error. It would be better if when the client fails to get
> a username from the system, it would simply prompt the user
> (just as if it had gotten a username, but that username had
> failed the authentication challenge with the repository).
>
> 2) If the client gets a username (by any means), that username
> should always be cached *unless* it fails an authentication
> challenge. In other words, if no challenge happens, but we have
> auth parameters available, then cache them -- it can't hurt.
[1] and [2] should solve the authentication issue and with [1] solved, any
SVN client can react smoothly instead of being forced to error out.
> It seems to me if we fix problem (1) from my list above, then TSVN
> will just Do The Right Thing automatically, right?
Yes, thanks that would be great.
> Folks, have I summarized this problem correctly, or am I missing
> something important here? Feedback welcome, please get to me before I
> file an issue... :-)
100% agreement from me. Did't switch my PC on last night, so here's my
response in the morning
Cheers
- Lübbe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 6 17:26:26 2003