Closed
Conversation
|
I haven't looked at the rest yet, but for API communication, @Kubuxu's unix socket proposal is very relevant: ipfs/notes#129 |
Member
|
Yeah, this change is going to be (at least) two parts, the first being making the API transport more flexible, and the second is the actual exposing of the corenet stuff. lets start working towards part 1, sound good @Kubuxu ? |
License: MIT Signed-off-by: Łukasz Magiera <magik6k@gmail.com>
License: MIT Signed-off-by: Łukasz Magiera <magik6k@gmail.com>
This was referenced Aug 25, 2016
Member
Member
Author
|
Yep, the other one implements the same thing. |
This file contains hidden or 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
5 participants
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.
This is continuation of #2005 , still WIP.
What it allows is to communicate in real-time using ipfs identities and libp2p. Currently the implementation uses websockets to communicate with daemon, and it implements channels over them, so the listener can handle more than 1 client at a time. Usage is still much like it was in #2005, but quite a few internals changed. I managed to set-up TAP tunnel over IPFS between 2 hosts using little helper program, so I think I can say that it at least works.
What needs to be done:
I'm opening this now so that people can see the progress and comment on what is done.