>>Hi!
>>
>>>Reading your Wish #1146 again, I'm satisfied with the way you've expressed it.
>>>
>>
>>I'm too. Just no mentioning of "Server" seems better, because client machine usually cannot control ANY caching on server by any way.
>>
>
>The FILE_FLAG_WRITE_THROUGH flag for CreateFile() causes any writes made to that handle to be written directly to the file without being buffered. The data is cached (stored in the disk cache); however, it is still written directly to the file. This method allows a read operation on that data to satisfy the read request from cached data (if it's still there), rather than having to do a file read to get the data. The write call doesn't return until the data is written to the file. This applies to remote writes as well--the network redirector passes the FILE_FLAG_WRITE_THROUGH flag to the server so that the server knows not to satisfy the write request until the data is written to the file.

Gerry,
Two things...

1) I think (quite sure) that Vlad is referring to HD controller cache, and I think that there is NO control other than "on/off" from software for that.

2) I'm assuming that you are quoting from some MS document in your post. Assuming so...
a) I wonder what "without being buffered. The data is cached..." is actually telling us?
b) There is still something amiss, and I assume it is in the description and not the actual operation. It is logically incorrect to make the cached record(s) READable when it has not yet been WRITten to the file. If I were guessing I would say that the successful WRITE return causes the cached record(s) to become READable from cache.

Your thoughts?