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: allow skipping upgrade steps for incoming connections #1502

Merged

Conversation

achingbrain
Copy link
Member

We already allow skipping upgrade steps for outgoing connections, this PR adds the same capability of incoming connections.

This is to support listeners for new transports like webtransport and webrtc that manage their own encryption and multiplexing.

We already allow skipping upgrade steps for outgoing connections,
this PR adds the same capability of incoming connections.

This is to support listeners for new transports like webtransport
and webrtc that manage their own encryption and multiplexing.
achingbrain added a commit to libp2p/js-libp2p-webtransport that referenced this pull request Nov 29, 2022
Uses `@fails-components/webtransport` to implement a listener for
this transport in node.

Depends on:

- [ ] Removal of console.log from `@fails-components/webtransport`
- [ ] Removal of segfaults from `@fails-components/webtransport`
- [ ] Fast event loop start/stop in `@fails-components/webtransport`
- [ ] libp2p/js-libp2p#1502
@mpetrunic mpetrunic merged commit 987c738 into master Nov 30, 2022
@mpetrunic mpetrunic deleted the feat/allow-skipping-upgrade-steps-for-incoming-connections branch November 30, 2022 09:01
mpetrunic added a commit that referenced this pull request Nov 30, 2022
@mpetrunic
Copy link
Member

@achingbrain did you cancel checks, didn't scroll so I didn't notice some checks were cancelled? Opened #1503 in case this wasn't ready

@achingbrain
Copy link
Member Author

Eh, weird - no, I didn't cancel checks.

@mpetrunic
Copy link
Member

Eh, weird - no, I didn't cancel checks.

false alarm, opened webtransport checks and got confused!

@achingbrain
Copy link
Member Author

Phew!

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

Successfully merging this pull request may close these issues.

2 participants