da24114ae0
The IPFS pin/update endpoint takes two arguments and usually unpins the first and pins the second. It is a bit more efficient to do it in a single operation than two separate ones. This will make the proxy endpoint hijack pin/update requests. First, the FROM pin is fetched from the state. If present, we set the options (replication factors, actual allocations) from that pin to the new one. Then we pin the TO item and proceed to unpin the FROM item when `unpin` is not false. We need to support path resolving, just like IPFS, therefore it was necessary to expose IPFSResolve() via RPC. |
||
|---|---|---|
| .. | ||
| cids.go | ||
| ipfs_mock.go | ||
| rpc_api_mock.go | ||
| sharding.go | ||
| test_test.go | ||
| test.go | ||