aab398f4f5
Do not use node's local storage if it is clear that an object will be removed anyway as a redundant. It requires moving the changing local storage logic from the validation step to the local target implementation. It allows performing any relations checks (e.g. object locking) only if a node is considered as a valid container member and is expected to store (stored previously) all the helper objects (e.g. `LOCK`, `TOMBSTONE`, etc). Signed-off-by: Pavel Karpy <carpawell@nspcc.ru> |
||
|---|---|---|
| .. | ||
| acl | ||
| delete | ||
| get | ||
| head | ||
| internal | ||
| put | ||
| search | ||
| util | ||
| common.go | ||
| metrics.go | ||
| response.go | ||
| server.go | ||
| sign.go | ||
| transport_splitter.go | ||