[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: login failure on WindowsNT
From: |
Derek R. Price |
Subject: |
Re: login failure on WindowsNT |
Date: |
Tue, 17 Oct 2000 14:48:35 -0400 |
address@hidden wrote:
> The method should be in the URI prefix since it really does identify
> the communication protocol. Save "cvs" for the standard CVS protocol;
> cvs-p perhaps for pserver, cvs-ssh for SSH, etc. The method name does
> not belong in the URI body.
My thought here was that without an overriding need for a URI immediately, it
might
be worth spending the time consolidating the protocols first. They're not very
different in the first place. Then cvs:// could mean connect to port 2401 and
ask
what authentication methods are valid. The server would respond with a list and
the client would use whatever it thinks is the most secure to authenticate and
set
up an encryption stream.
I'm thinking :ext: would still need its own URI prefix. And probably :local:.
pserver, gserver, and kserver are almost identical except for the auth methods,
though.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden OpenAvenue ( http://OpenAvenue.com )
--
There are plenty of businesses like show business.
There are plenty of businesses like show business.
There are plenty of businesses like show business...
- Bart Simpson on chalkboard, _The Simpsons_
- Re: login failure on WindowsNT, (continued)
RE: login failure on WindowsNT, John Scott - Outlook, 2000/10/12
Re: login failure on WindowsNT, Derek R. Price, 2000/10/12
Re: login failure on WindowsNT, Derek R. Price, 2000/10/12
Re: login failure on WindowsNT, rsalz, 2000/10/12
- Re: login failure on WindowsNT,
Derek R. Price <=