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

Allow for custom data transfer mechanisms #109

Closed
MarcoPolo opened this issue Apr 28, 2023 · 3 comments
Closed

Allow for custom data transfer mechanisms #109

MarcoPolo opened this issue Apr 28, 2023 · 3 comments

Comments

@MarcoPolo
Copy link

Please correct me if I'm wrong, but it seems like bitswap is always activated if you provide a libp2p object to the helia constructor. I would like a way to either:

  1. Disable bitswap, and allow me to provide my own custom blockstore that may or may not use bitswap. If we do this it would be nice to expose the helia's BlockStorage so I can reuse that code with my own custom bitswap.
  2. Allow for a custom bitswap to be passed in as an option (and maybe even allow for it to be set to false so it's disabled like 1).

I would like this so I can plug in alternative data transfer mechanisms like using the HTTP gateway api.

@BigLep
Copy link
Contributor

BigLep commented May 1, 2023

@MarcoPolo : is this a duplicate of #98 ?

@MarcoPolo
Copy link
Author

Yes, thanks. I didn't find that one. Closing in favor of the other one.

@SgtPooki
Copy link
Member

@MarcoPolo This is now possible on the helia@next branch. pls let us know if you try it out.

achingbrain added a commit that referenced this issue Jan 8, 2024
Remove deprecated interfaces for newer versions.
achingbrain pushed a commit that referenced this issue Jan 8, 2024
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

No branches or pull requests

3 participants