5b332a87be
Dropping from a cluster drops from every node of the cluster. Including nodes that the cluster does not think have the content. This is different from GET and CHECKPRESENT, which do trust the cluster's location log. The difference is that removing from a cluster should make 100% the content is gone from every node. So doing extra work is ok. Compare with CHECKPRESENT where checking every node could make it very expensive, and the worst that can happen in a false negative is extra work being done. Extended the P2P protocol with FAILURE-PLUS to handle the case where a drop from one node succeeds, but a drop from another node fails. In that case the entire cluster drop has failed. Note that SUCCESS-PLUS is returned when dropping from a proxied remote that is not a cluster, when the protocol version supports it. This is because P2P.Proxy does not know when it's proxying for a single node cluster vs for a remote that is not a cluster. |
||
|---|---|---|
| .. | ||
| Chunked | ||
| AWS.hs | ||
| Chunked.hs | ||
| Encryptable.hs | ||
| ExportImport.hs | ||
| Git.hs | ||
| Hooks.hs | ||
| Http.hs | ||
| Messages.hs | ||
| P2P.hs | ||
| Path.hs | ||
| ReadOnly.hs | ||
| Special.hs | ||
| Ssh.hs | ||
| ThirdPartyPopulated.hs | ||