Use global cache passed through corestore if available #163
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relies on holepunchto/hypercore#535 and holepunchto/corestore#94 (so draft PR)
Exposes the
globalCacheon its autocore sessions, if the corestore it was passed exposes it. This makes them compatible with the hypercore (with the linked PR). In particular, views generated from this autobase will use the globalCache (assuming hyperbee PR holepunchto/hyperbee#161 is used).This makes the
maxCacheSizeopt redundant, so I removed it. Technically this is a breaking change, but it was an unofficial option anyway (and no harm done if it's still passed in, it's just ignored).