Unverified Commit 4611e41e authored by @RubenKelevra's avatar @RubenKelevra Committed by GitHub

Apply suggestions from code review

Co-Authored-By: default avatarWill <willscott@gmail.com>
parent 0c08e067
...@@ -544,7 +544,7 @@ You can read more in the [datastore](./datastores.md#badgerds) documentation. ...@@ -544,7 +544,7 @@ You can read more in the [datastore](./datastores.md#badgerds) documentation.
### State ### State
Experimental Experimental
Allows to create directories with an unlimited number of entries - currently Allows creating directories with an unlimited number of entries - currently
size of unixfs directories is limited by the maximum block size size of unixfs directories is limited by the maximum block size
### Basic Usage: ### Basic Usage:
...@@ -570,13 +570,13 @@ ipfs config --json Experimental.ShardingEnabled true ...@@ -570,13 +570,13 @@ ipfs config --json Experimental.ShardingEnabled true
Experimental, default-disabled. Experimental, default-disabled.
Utilizes pubsub for publishing ipns records in real-time. Utilizes pubsub for publishing ipns records in real time.
When it is enabled: When it is enabled:
- IPNS publishers push records to a name-specific pubsub topic, - IPNS publishers push records to a name-specific pubsub topic,
in addition to publishing to the DHT. in addition to publishing to the DHT.
- IPNS resolvers subscribe to the name-specific topic on first - IPNS resolvers subscribe to the name-specific topic on first
resolution and receive subsequently published records through pubsub in real-time. This makes subsequent resolutions instant, as they are resolved through the local cache. Note that the initial resolution still goes through the DHT, as there is no message history in pubsub. resolution and receive subsequently published records through pubsub in real time. This makes subsequent resolutions instant, as they are resolved through the local cache. Note that the initial resolution still goes through the DHT, as there is no message history in pubsub.
Both the publisher and the resolver nodes need to have the feature enabled for it to work effectively. Both the publisher and the resolver nodes need to have the feature enabled for it to work effectively.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment