Hi Karl,
since we are having the same problem here (5 developers on Win98), we are
very much interested into getting that patch into SVN too.
John Locke wrote:
> > What's holding up the acceptance of Stefan's patch?
>
> Probably just that people are busy and didn't know how important it
> was... Do you or Stefan have a reference for the patch?
Here's the first thread about Stefan's patch:
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgId=256035
the second one:
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgId=268492
If you search the dev archive for "win98" or "uid" you will find more people
having that problem. Most of them, expecting a fault in TortoiseSVN complain
on the TSVN dev list. We point them to the subversion list, so that the SVN
deveoplers will become aware of the problem, but until now that didn't help
much :-)
Unfortunately many people don't ask for assistance here, but rather give up
using TSVN or SVN at all.
IMHO Subversions login handling is not really user friendly. For instance:
If I connect to a password protected repository for the fist time,
Subversion tries to connect with my windows user ID (yes I know about
--username) and asks for my windows password. If this fails, SVN asks me for
another UID and the corresponding password.
On a Win98 client Subversion cannot get a UID and fails instantly instead of
trying to request the necessary information from the user as it does on
other OSes if the login fails for some other reason.
Not very smart, from a users point of view.
A different thing is, that with TSVN as a client, I have no chance of
telling SVN beforehand which UID I want to use when I connect to a
repository, until the login credentials are cached by SVN. In this case I
have to let the first login attempt fail (confusing, but I know that by
now), before I get my second chance to enter the correct UID/password.
I don't know if TSVN has a chance to work around the above behaviour (I'll
ask on the TSVN list), but I think it would be nice, if upon the first
connect, the SVN API would provide a response to the client like:
"trying to connect with username:" <Username>.
If SVN couldn't get a UID (eg. win98), the username string would be blank.
Now different clients can react differently:
- The command line client can still try to connect to the repository
immediately using the provided username, asking only for a password, or ask
for a uid/password if the username is blank.
- TSVN (or any other GUI client) can pop up a username/password dialog,
where the UID is already filled in.
This way we could get around that confusing "fail once, success later"
behaviour.
Cheers
- Lübbe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 22 10:55:34 2003