[cifs-protocol] SMB1 -- proper client behavior when it does not hold an oplock

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Dochelp! I'm hoping you can help clarify some points about proper SMB1 (and maybe SMB2?) client behavior when it does not hold an oplock (at least one that allows write caching). My understanding has always been that when a client does not have

[cifs-protocol] SMB1 -- proper client behavior when it does not hold an oplock

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry for the duplicate emails, but I sent this to the wrong dochelp address before. Let me try again... Hi Dochelp! I'm hoping you can help clarify some points about proper SMB1 (and maybe SMB2?) client behavior when it does not hold an oplock (at

Re: [cifs-protocol] SMB1 -- proper client behavior when it does not hold an oplock

Hello Jeff, Thank you for your inquiry about File sharing protocols. One of the Open specifications team member will contact you soon. Regards, Sreekanth Nadendla Microsoft Windows Open Specifications -Original Message- From: Jeff Layton [mailto:jlay...@poochiereds.net]