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

feat: TCP client in Brave #754

Merged
merged 16 commits into from
Sep 13, 2019
Merged

feat: TCP client in Brave #754

merged 16 commits into from
Sep 13, 2019

Conversation

lidel
Copy link
Member

@lidel lidel commented Sep 9, 2019

Parent: #716

TODO

Known issues

TCP transport (client)

brave-win-2019-08-30--14-41-18

Local DNS discovery (client)

mdns-in-extension-2019-09-03--14-57-26

ws-star is optional, should not break boot process
This switch to js-ipfs before PR-2379

ipfs/js-ipfs#2379 switched ipfs.add
to ipfs._addAsyncIterator and it broke /api/v0/add exposed by embedded
js-ipfs in Brave.

It seems old polyfills are no longer enough. Real fix requires more time
to investigate, so for now we switch to version before js-ipfs/PR-2379.

Used js-ipfs commit is from ipfs/js-ipfs#2304 before it
was rebased on top of master after PR-2379, making it the last safe
version.

Real fix will be tracked in
#757
- discovers free TCP port for incoming connections
- discovers network IPs via WebRTC APIs provided by the browser
@lidel lidel marked this pull request as ready for review September 13, 2019 12:34
@lidel
Copy link
Member Author

lidel commented Sep 13, 2019

Known issues will be tracked in respective issues, TCP transport itself is ready for Beta test run.

@lidel lidel merged commit 8f7eda4 into master Sep 13, 2019
@lidel lidel deleted the feat/tcp-transport-in-brave branch September 13, 2019 18:38
@lidel lidel added the area/brave Issues related to Brave Browser label Oct 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/brave Issues related to Brave Browser
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant