7a839a983a
Support selecting what remote to proxy for each top-level P2P protocol message. This only needs to be extended now to support fanout to multiple nodes for PUT and REMOVE, and with a remote that fails for LOCKCONTENT and UNLOCKCONTENT. But a good first step would be to implement CHECKPRESENT and GET for clusters. Both should select a node that actually does have the content. That will allow a cluster to work for GET even when location tracking is out of date. |
||
|---|---|---|
| .. | ||
| Address.hs | ||
| Annex.hs | ||
| Auth.hs | ||
| IO.hs | ||
| Protocol.hs | ||
| Proxy.hs | ||