Skip to content
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.

level 2 - rpc style json api #10

Closed
dignifiedquire opened this issue Dec 7, 2015 · 4 comments
Closed

level 2 - rpc style json api #10

dignifiedquire opened this issue Dec 7, 2015 · 4 comments

Comments

@dignifiedquire
Copy link
Collaborator

No description provided.

@RichardLitt
Copy link
Contributor

Can you give a bit more context than the title? I'm not sure what this issue means.

@daviddias
Copy link
Contributor

What is level 1 and level 2 API spec? I guess my question is "why levels"?

@dignifiedquire
Copy link
Collaborator Author

Level 1 was discussed as being the transport agnostic variant, just as type signatures. And Level 2 would be the specific variant, on for http one for cli one for json rpc, etc.

@daviddias
Copy link
Contributor

Got it, thank you for clarifying. The API specs were moved to ipfs/specs (as noted here #11) and I've updated it here ipfs/specs#65. Let's move the discussion over there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dignifiedquire @RichardLitt @daviddias