Windows 7常量刷新SMB 2.002目录 [英] Windows 7 constant refresh of SMB 2.002 directory

问题描述

我在文件系统不支持change notify的系统上实现了非Windows SMB 2.002服务器。   SMB2规范描述了如果后备存储不提供更改
通知则返回STATUS_NOT_SUPPORTED有效的情况。

I have implemented a non-Windows SMB 2.002 server on a system whose file systems do not support change notify.  The SMB2 specification describes situations where it is valid to return STATUS_NOT_SUPPORTED if the backing store does not provide change notifications.

摘自第3.3.5.19节：

Excerpt from section 3.3.5.19:

"如果底层对象存储不支持更改通知，则服务器必须使用STATUS_NOT_SUPPORTED使此请求失败。"

"If the underlying object store does not support change notifications, the server MUST fail this request with STATUS_NOT_SUPPORTED."

我的问题是将STATUS_NOT_SUPPORTED返回到Windows 7客户端似乎将客户端设置为目录上的刷新循环，直到资源管理器窗口关闭。  正如您可能想象的那样，快速文件刷新会导致服务器上的DOS，因为
的网络接口和CPU瓶颈以及使用户很难在Explorer窗口中执行操作（如重命名）一个文件。）

My problem is that returning STATUS_NOT_SUPPORTED to a Windows 7 client appears to set the client into a refresh loop on the directory until the Explorer window is closed.  As you might imagine, the rapid file refreshes cause a DOS on the server because of network interface and CPU bottle-necking as well as making it very difficult for the user to perform operations in the Explorer window (like renaming a file.)

任何人都可以解释如何避免这种无限刷新循环而不要求服务器支持更改通知吗？

Can anyone explain how to avoid this infinite refresh loop without requiring that the server support change notifications?

推荐答案

嗨Charles，

Hi Charles,

感谢您联系Microsoft Open Specification Forum。 我们已收到上述请求。  开放式规范支持团队的其中一位工程师将很快与您联系。 

Thank you for contacting Microsoft Open Specification Forum.  We have received the request above.  One of the engineers from the open specifications support team will be in contact shortly. 

谢谢，

Nathan Manis

Nathan Manis

这篇关于Windows 7常量刷新SMB 2.002目录的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！