4 ms·

I didn't say your experience was "wrong" though? That doesn't even make sense; your experience is what it is. I only said your reasoning about your experience

I didn't say your experience was "wrong" though? That doesn't even make sense; your experience is what it is. I only said your reasoning about your experience was wrong, i.e. you should be blaming the applications and not the OS (whether they're made by MS or anyone else). Regarding antiviruses: yes, of course I am. That's why they should be opening the files with FILE_SHARE_DELETE, and properly handling the edge cases. Unless you're telling me it's impossible (which I strongly suspect isn't the case, but then again I've never tried to write an AV myself), I don't see how it's the OS's fault. This flag and the associated functionality obviously exists for a reason, right? It's not an OS design flaw if people aren't using it, is it? People can refuse to play along with anything... that doesn't mean the OS is flawed.

asveikau 10y ago
Sharing modes don't help with the STATUS_DELETE_PENDING issue. Nor does it let you delete a directory while children are open. Also some AV will duplicate your handles, meaning they get the same sharing mode you asked for. > This flag and the associated functionality obviously exists for a reason, right? It's the kind of stuff that sounds reasonable when you hear about it, but when you see it put into practice is the source of way too many bugs.
- wfunction 10y ago
  > Sharing modes don't help with the STATUS_DELETE_PENDING issue. Maybe I misunderstood the problem. But I think my reasoning holds regardless? To be clear, it seems you're talking about a situation where an app is trying to delete and re-create a file, and an AV is scanning the file in between, hence a recreation fails. But with their file system filter drivers, AVs can detect such recreation attempts, so they should be able to handle it properly. So isn't it their fault for not doing so? > Nor does it let you delete a directory while children are open. Right, but same as above: there exists functionality to detect this, right? So if it isn't used, whose fault is it?

asveikau 10y ago

Sharing modes don't help with the STATUS_DELETE_PENDING issue. Nor does it let you delete a directory while children are open. Also some AV will duplicate your handles, meaning they get the same sharing mode you asked for. > This flag and the associated functionality obviously exists for a reason, right? It's the kind of stuff that sounds reasonable when you hear about it, but when you see it put into practice is the source of way too many bugs.

wfunction 10y ago
> Sharing modes don't help with the STATUS_DELETE_PENDING issue. Maybe I misunderstood the problem. But I think my reasoning holds regardless? To be clear, it seems you're talking about a situation where an app is trying to delete and re-create a file, and an AV is scanning the file in between, hence a recreation fails. But with their file system filter drivers, AVs can detect such recreation attempts, so they should be able to handle it properly. So isn't it their fault for not doing so? > Nor does it let you delete a directory while children are open. Right, but same as above: there exists functionality to detect this, right? So if it isn't used, whose fault is it?