Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Wed, 27 Feb 2002 11:37:38 +0000 (UTC), Brian Smith <brian-l-smith at uiowa.edu> wrote: >1. I had to change the signature of the get_protocol_interface function to: > struct protocol_interface *get_protocol_interface( > const char * method /* e.g. "gserver", "sspi", > const struct server_interface *server); >this caused a lot of little changes (one for each protocol). load_protocol only knows the protocol name that the user sent, which is the same as the dll name. find_authentication_mechanism makes this even more explicit by passing in the name of the dll as the protocol name... I'm not keen on putting any kind of mapping in the registry because it would require that the client is configured in some way - the client side currently works OK without any extra configuration... you can copy the cvs.exe and any protocol dlls you need & just start working. A text config file might work... something like: [gserver] ;protocol_dll = sspi_protocol.dll protocol_dll = gserver_protocol.dll ident_string = BEGIN GSSAPI [sspi] protocol_dll = sspi_protocol.dll ident_string = BEGIN SSPI etc.. Then it could be copied around with the cvs.exe and the clients would still work. It also removes the need for an extra flag (since you could just comment out the one you didn't want to use). Can you verify that your changes to sspi are compatible with the current CVS tree? I really don't want to change the sspi protocol again... rc2 is planned for either friday or monday & that should be the last one before release. Tony _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs