Support WebRTC transport

Open
#1,701 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust, wasm
Domain
networking

Research direction

The issue does not name files, tests, or an entry point. Start by reading the repository’s transport implementation and architecture to find where a WebRTC transport would fit. Done means supporting direct peer-to-peer browser communication without a server intermediary; the issue gives no further requirements.

Written by the indexing model from the issue text.

Description

For use cases like direct p2p browser - browser communication without a server intermediary.

Dominant language
Rust
Stars
336
Forks
48
Avg merge
10h 39m
Merged PRs (30d)
203

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bytecodealliance/wrpc

All issues in bytecodealliance/wrpc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.