[EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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_
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
