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

Tracking Issue - WebRTC direct in Node.js #2581

Open
6 of 7 tasks
2color opened this issue Jun 7, 2024 · 1 comment
Open
6 of 7 tasks

Tracking Issue - WebRTC direct in Node.js #2581

2color opened this issue Jun 7, 2024 · 1 comment
Labels
kind/tracking A meta-issue for tracking work

Comments

@2color
Copy link
Contributor

2color commented Jun 7, 2024

Background

WebRTC-direct is currently only supported in browsers as mentioned in package.

This is a tracking issue for adding support for WebRTC-direct in Node.js, which would allow browsers to dial Node.js directly (without circuit relay and signalling) without needing for a TLS certificate as in the case of WebSockets.

Dependencies

This require changes to both https://github.com/murat-dogan/node-datachannel and https://github.com/paullouisageneau/libdatachannel to allow SDP Munging.

Related PRs/issues:

@2color 2color added the need/triage Needs initial labeling and prioritization label Jun 7, 2024
@achingbrain
Copy link
Member

There is good news when all of the above PRs are applied:

image

achingbrain added a commit that referenced this issue Jun 7, 2024
achingbrain added a commit that referenced this issue Jun 7, 2024
@achingbrain achingbrain added kind/tracking A meta-issue for tracking work and removed need/triage Needs initial labeling and prioritization labels Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/tracking A meta-issue for tracking work
Projects
None yet
Development

No branches or pull requests

2 participants