Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unique Blockstores: RetrievalMarket #342

Merged
merged 4 commits into from
Jul 28, 2020

Conversation

hannahhoward
Copy link
Collaborator

Goals

This is basically analogous to #341, but for retrieval market

Implementation

Client:

  • Inject multistore instead of blockstore
  • Add storeID to retrieve method
  • Use transport configurer to make sure writes go to the right store

Provider

  • inject multistore instead of blockstore
  • create a store for the deal upon acceptance of the deal
  • read into this store when unsealing
  • configure data transfer to use the right multistore via configurer
  • delete store when done (New event sequence in cleanup functions)

@hannahhoward hannahhoward force-pushed the feat/custom-block-stores-retrieval branch from 0e48fa7 to cf6b0a7 Compare July 28, 2020 05:54
@magik6k magik6k changed the base branch from feat/custom-block-stores to master July 28, 2020 10:36
use multistore throughout retrieval market -- setup transport configurer, storeID piping, automatic
blockstore clearing, etc.
support using regular blockstores on client side for IPFS compatibility
@magik6k magik6k force-pushed the feat/custom-block-stores-retrieval branch from cf6b0a7 to b81f824 Compare July 28, 2020 10:40
@magik6k magik6k merged commit caae3fd into master Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants