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

routing: rework interfaces to make separation easier #3107

Merged
merged 1 commit into from
Aug 21, 2016

Conversation

whyrusleeping
Copy link
Member

I've started to work on separating the content routing layer and the peer routing layer. The third bit that we glom into our current routing interface deals with direct values, i think thats what @diasdavid was starting to call the record store, but i'm not sure its the same scope. Definitely want some feedback here.

cc @jbenet @diasdavid

License: MIT
Signed-off-by: Jeromy why@ipfs.io

License: MIT
Signed-off-by: Jeromy <why@ipfs.io>
@whyrusleeping whyrusleeping added the status/in-progress In progress label Aug 20, 2016
@daviddias
Copy link
Member

Yeah, seems on the right track to break Peer Routing and Content Routing into separate parts, so that we can have other types of Content Routing (therefore super fast providing)

See https://github.com/libp2p/interface-record-store and https://github.com/libp2p/interface-peer-routing also for more context.

@whyrusleeping whyrusleeping added the need/review Needs a review label Aug 20, 2016
@whyrusleeping whyrusleeping merged commit 37cf360 into master Aug 21, 2016
@whyrusleeping whyrusleeping deleted the feat/routing/interfaces branch August 21, 2016 01:45
@whyrusleeping whyrusleeping removed the status/in-progress In progress label Aug 21, 2016
@ghost ghost mentioned this pull request Dec 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/review Needs a review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants