Quote:
Originally Posted by Quoth
Source for this astounding claim?
|
Read the docs...Microsoft has hundreds of pages on how their networking works, and there are all sorts of fun things you can learn.
Mostly, it's related to the code that was added to allow a user to access a share on the local machine without incurring any penalty from the network stack. This has been expanded so that NTFS and ReFS semantics are the same regardless of whether you are local or remote.
Unless a program specifically checks to see if there is a reparse point with a non-local target somewhere between the root of the drive and the target file, there is no way to tell if the target is local or not. Usually, the only clue is when deleting files from Explorer you get the "permanently delete" warning just like you always do if there is no recycle bin.
It's not that Windows doesn't actually know the filesystem is remote...it's just that the behavior is same as a local filesystem, because Windows knows the other end supports all the same functions.