Karl Fogel wrote:
>Peter Schuller <peter.schuller@infidyne.com> writes:
>
>
>>Another issie is if the username and password on the server has become
>>invalid since the last time you used the repository. Will svn prompt or
>>fail?
>>
>>
>
>Yeah, this is a variation of a general scenario I realized this
>morning.
>
>You might write your script to use --username and --password, and we
>might make Subversion fail out if they are invalid, but what if the
>server's entire authentication method changes after the working copy
>is checked out? For regular users, one reasonable behavior is to
>prompt for new information -- it's very convenient. But then we're
>back to wanting a --non-interactive flag for scripts...
>
>Mrm. Hmmm.
>
>We can't be the first project to encounter this problem. Is there
>already a convention about how to handle it, or do different programs
>do different things?
>
>(Re detecting whether stdin is a tty, is that really reliable? We'd
>need to add it to APR, at any rate...)
>
>
I think the first order of business is to make a clean separation
between the libraries and the client program. IIRC, right now the prompt
is coming from the RA lib. Instead, the lib should simply return an
error if authentication fails; then the client can decide about
prompting or not.
The next problem is what to do with the failure in the client. IMHO, if
any auth tokens were passed in explicitly on the command line, it should
not prompt -- the user had her shot, and missed.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 7 22:16:37 2002