[Cvs-dev] Re: cvs-chpass.patch (former: cvs-passwd.patch)

[Derek R. Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Prasad J Pandit wrote:
>> 2.  In client mode, accept as options all of the options CVSNT accepts
>> in addition to your new options, and forward them to the server,
>> allowing the server to reject them if it wishes.  These are (from
>> <http://www.cvsnt.org/manual/html/passwd.html>): -a, -x, -X, -r
>> SYS_USER, -R, and -D DOMAIN.  The complete CVSNT syntax is:
>>
>>     cvs passwd [-axXR] [-r SYS_USER] [-D DOMAIN] [USERNAME]
> 
>   Okay!
> 
> But why let server reject the (invalid)options, shouldn't that be done
> at client side? Or
> 
> It'll be more clear, if you could give me some case(s) when server
> rejects the (invalid)options??

The idea is that the CVS client would pass -axXR, -r SYS_USER, -D
DOMAIN, and any new options through to the server.  Then, a CVSNT server
could reject your new options, and a CVS server could reject CVSNT
specific options, but the client would be agnostic about what kind of
server it was talking to.

>> 3.  In local and server mode, accept only the options you wish to
>> implement, including any options not implemented by CVSNT, but if you
>> have implemented any similar functionality, try to merge it under the
>> same syntax/options as CVSNT.
> 
>  Ummn... I didn't get this.

In server mode (and local mode), you would want to reject the CVSNT
option that the client accepted, since they are not handled.  This way,
a CVSNT client could pass options the CVS server doesn't handle and the
user should get a friendly message about the failure.

Regards,

Derek
- --
Derek R. Price
CVS Solutions Architect
Get CVS support at Ximbiot <http://ximbiot.com>!
v: +1 248.835.1260
f: +1 248.835.1263
<mailto:address@hidden>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEoULGLD1OTBfyMaQRAmAeAJ9xkcWfzwgtepJdp5JKBmnvYbfxOACaAgfQ
br7+9KJzCYldPdPDlTNHLu4=
=fdE3
-----END PGP SIGNATURE-----