diff options
| author | Viktor Trón <viktor.tron@gmail.com> | 2018-10-03 20:59:41 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-10-03 20:59:41 +0800 |
| commit | e5677114dc7461fe39ebe353a4657aa4cb03fde4 (patch) | |
| tree | 8605f9a8b726b158fd01b4befced1e3ba92ca1f9 /swarm/network/README.md | |
| parent | 303b99663e963a520aaa44eca68e042d9fe230af (diff) | |
| parent | de01178c18766b9f744acc94fe2b96804f998e40 (diff) | |
| download | go-tangerine-e5677114dc7461fe39ebe353a4657aa4cb03fde4.tar go-tangerine-e5677114dc7461fe39ebe353a4657aa4cb03fde4.tar.gz go-tangerine-e5677114dc7461fe39ebe353a4657aa4cb03fde4.tar.bz2 go-tangerine-e5677114dc7461fe39ebe353a4657aa4cb03fde4.tar.lz go-tangerine-e5677114dc7461fe39ebe353a4657aa4cb03fde4.tar.xz go-tangerine-e5677114dc7461fe39ebe353a4657aa4cb03fde4.tar.zst go-tangerine-e5677114dc7461fe39ebe353a4657aa4cb03fde4.zip | |
Merge pull request #17796 from epiclabs-io/mru-feeds
swarm/storage/feeds: Renamed MRU to Swarm Feeds
Diffstat (limited to 'swarm/network/README.md')
| -rw-r--r-- | swarm/network/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/swarm/network/README.md b/swarm/network/README.md index e9c9d30d0..684ad0c8c 100644 --- a/swarm/network/README.md +++ b/swarm/network/README.md @@ -37,7 +37,7 @@ Using the streamer logic, various stream types are easy to implement: * live session syncing * historical syncing * simple retrieve requests and deliveries -* mutable resource updates streams +* swarm feeds streams * receipting for finger pointing ## Syncing @@ -57,7 +57,7 @@ receipts for a deleted chunk easily to refute their challenge. - syncing should be resilient to cut connections, metadata should be persisted that keep track of syncing state across sessions, historical syncing state should survive restart - extra data structures to support syncing should be kept at minimum -- syncing is organized separately for chunk types (resource update v content chunk) +- syncing is not organized separately for chunk types (Swarm feed updates v regular content chunk) - various types of streams should have common logic abstracted Syncing is now entirely mediated by the localstore, ie., no processes or memory leaks due to network contention. |