dynamic transports
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 63.2k
- Forks
- 10.3k
- Avg merge
- 11d 20h
- Merged PRs (30d)
- 2
Description
Transports must be dynamic to provide transports independently.
In my opinion, by making dynamic transports, it is possible to add custom transports such as tcp, mqtt gprc, etc.
But this issue is not implemented in engine.io (or there is no suitable document for it)
Solution
I think providing transport independently, such as engineio-websocket-transport, could be better than the current situation and make it possible to implement different transports.
Contributor guide
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
Start by reviewing engine.io's existing transport implementation and documentation, since the issue names no files or tests. Define the integration boundary for independently provided transports and document or demonstrate how custom transports such as TCP or MQTT would be supported; the issue is done when that design is implemented and usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100