Ah, yes, I had seen the protocol documents, but I guess I assumed (I keep doing that) they had been created from work on the Unix version. I have revisited them and here are a couple of excerpts to support my position.
>From the "Introduction to Responses" section of cvsclient_5.html: "Any set of responses always ends with `error' or `ok'. This indicates that the response is over." And below, in the "Responses" section , near the bottom of the list is: "error errno-code ` ' text \n The command completed with an error. errno-code is a symbolic error code (e.g. ENOENT); if the server doesn't support this feature, or if it's not appropriate for this particular message, it just omits the errno-code (in that case there are two spaces after `error'). Text is an error message such as that provided by strerror(), or any other message the server wants to use." This is precisely what the Unix version does in my problem case, and is just what Eclipse needs (in addition to the "E" error message). CVSNT should follow the "E" message with at least "error \n". -----Original Message----- From: Tony Hoyle [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 23, 2002 10:53 AM To: 'Schmidt, Martin' Cc: '[EMAIL PROTECTED]' Subject: RE: [Cvsnt] Re: CVSNT error handling and Eclipse/WSAD branch brow sing > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Schmidt, Martin > Posted At: 22 May 2002 20:45 > Posted To: cvsnt > Conversation: [Cvsnt] Re: CVSNT error handling and Eclipse/WSAD branch > browsing > Subject: [Cvsnt] Re: CVSNT error handling and Eclipse/WSAD branch > browsing >the error is as likely to break other clients as fix anything. > > I thought the Unix version of CVS was the defintion of CVS. > Is there some > generic documentation/standard that CVSNT and Unix CVS are > both based on? I > was assuming that existing clients were written to support > Unix CVS, and > that if it behaved this way that CVSNT would want to follow suit to be > compatible. At any rate, CVSNT was obviously not written based on > documentation, it was ported from Unix CVS. > Try: Client/Server protocol specification: http://www.loria.fr/~molli/cvs/doc/cvsclient_5.html RCS file format: http://www.nmt.edu/tcc/swinv/rcs/5.7/man/rcsfile.5.html cvsnt will stick to these documents, and will (as far as possible) maintain a command line interface that applications can call that looks identical to unix cvs. As long as Unix cvs can talk to cvsnt and vice-versa then that's a good level of compatibility. Trying to cope with all the quirks of 3rd party implementations would rapidly become a nightmare. If you can find somewhere that cvsnt breaks this then I'll happily fix it... Tony (currently at work, reply to my normal email address [EMAIL PROTECTED]). _______________________________________________ Cvsnt mailing list [EMAIL PROTECTED] http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
