WASM transports
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 35
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
With the rise of WASM this may offer a different approach to isolating transports and composing transports written in different languages. I wonder if any thought has been put into this?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue contains no file, test, or entry point to start from. Begin by reviewing the XTP repository and the transport protocol, then determine whether WASM can isolate transports and compose implementations written in different languages. Done would require a defined approach and agreed scope, not just an exploratory proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100