-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeremy Allison schrieb: > On Sun, Mar 11, 2007 at 12:14:48AM +0100, Stefan (metze) Metzmacher wrote: >> can't we out that logic into the client, so when the client >> get the redirect from a server with unix extentions then >> it converts the redirect url when he talks to a server without >> unix extentions support. > > Yes, that's exactly what I'm coding up right now. > Wait for the check-in :-).
good:-) >> This way the communication over a connection with unix extentions >> would be consistent. >> >> And the client needs to have some logic anyway as >> \server\share/unix/path isn't valid for connecting to a server without >> unix extentions. > > I'm planning to make it \server\share\path/to/unix/file, > but the server code will also accept /server/share/path/to/unix/file > on the principle of be liberal in what you accept. Then you need 2 code pathes in the server code, and one will never be tested. I think it's not the best design to allow 2 different things in one protocol-field. why not reply and accept a full path with the unix '/' delimiters, when we are in unix mode and a full path with windows '\' delimiters in non-unix mode. metze -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFF88KAm70gjA5TCD8RAhVgAJ9BfUKc2wuZjXKpV10RBrKCwAwssACghGwr MW43GL23GXCFeiVLBC004YA= =9UGe -----END PGP SIGNATURE----- _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
