-
Notifications
You must be signed in to change notification settings - Fork 467
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
Support HTTP REST API #3098
Labels
C-dev-productivity
Category: Developer productivity
C-ux
Category: Anything related to user experience
Comments
This was referenced Jul 23, 2019
Closed
Any progress or plan on this? |
Hey @ridewindx there is some progress - a WIP design document: https://docs.google.com/document/d/1ANnTHOU-8612ayvvS7Ru4B1L4voojLE0R0TQ8zF1x5s/edit# |
Status: See filecoin-project/go-http-api -- further development is on hold for now. |
@shannonwells @anorth I can pick this up if you can share what's remaining to be done |
The time isn't right for this yet.
…On Wed, 15 Apr 2020 at 06:07, Deepak Garg ***@***.***> wrote:
@shannonwells <https://github.com/shannonwells> @anorth
<https://github.com/anorth> I can pick this up if you can share what's
remaining to be done
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3098 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADMW6X3C6DMIFHVBQUG56DRMS67TANCNFSM4IF4VR3A>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-dev-productivity
Category: Developer productivity
C-ux
Category: Anything related to user experience
Description
Related spec issue: filecoin-project/specs#400
The current HTTP RPC API from go-ipfs-cmds was never designed as a general purpose API framework and is awkward for developer-users:
A standard HTTP api could address these issues and offer the possibility of cross-implementation compatibility for tools that communicate with a node.
Scope
The goals of this effort would be:
Risks + pitfalls
A lot of work to replace a working but somewhat awkward existing API. Helpful for longer term adoption and support of 3rd parties building on Filecoin
Where to begin
@eingenito working on a draft of such an API for review by the team and any other interested parties.
The text was updated successfully, but these errors were encountered: