Skip to content
This repository has been archived by the owner on Feb 26, 2021. It is now read-only.

feat: Rewrite from SIO+ws-relay to protobuf+p2p-circuit #43

Closed
wants to merge 16 commits into from

Conversation

mkg20001
Copy link
Member

@mkg20001 mkg20001 commented Jan 23, 2018

This PR is a full rewrite of libp2p-websocket-star.
Major changes:

  • No more socket.io
  • p2p-circuit is handling relay

Server pr: libp2p/js-libp2p-websocket-star-rendezvous#11

(If the code does not work this might be because it says draft and thats because I didn't test)
@ghost ghost assigned mkg20001 Jan 23, 2018
@ghost ghost added the in progress label Jan 23, 2018
@mkg20001
Copy link
Member Author

PR is ready for review

@mkg20001
Copy link
Member Author

mkg20001 commented Feb 4, 2018

@libp2p/javascript-team Anybody mind reviewing this (and server pr)? Can I just merge that?

@daviddias
Copy link
Member

@mkg20001 I need to review this PR and make sure it follows the model we have to achieve with libp2p/js-libp2p#130. I plan to prioritize that and do it this week.

message IdentifyResponse {
required string id = 1;
required string pubKey = 2;
required bytes signature = 3;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not have all the same fields as the identify protocol?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not the same identify protocol. Additionally in the libp2p-identify protocol the public keys never get exchanged.

@daviddias
Copy link
Member

Status Update:

This PR is currently blocked on libp2p/js-libp2p#159 which will bring things like DI setup to libp2p. Lot's of work happening there.

Also, we will only be confident to move into a p2p-circuit solution once ipfs/interop#6 is completely done.

Things that are part of this PR that are not part of the migration to p2p-circuit should happen in a separate PR, i.e Fixing memory leaks. @mkg20001 can you do that?

@mkg20001
Copy link
Member Author

mkg20001 commented Mar 6, 2018

@diasdavid The memory leaks are mainly socket.io's fault.
I can try to split this pr up into multiple prs.

@daviddias
Copy link
Member

@mkg20001
Copy link
Member Author

mkg20001 commented Apr 3, 2018

I think this is no longer needed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants