Future proof: TCP vanilla transport
Open
Nobody has claimed this yet.
package:engine.io
- Dominant language
- TypeScript
- Stars
- 63.2k
- Forks
- 10.3k
- Avg merge
- 11d 20h
- Merged PRs (30d)
- 2
Description
Inspired from your post on socket.io 1.0:
Alternative transports such as vanilla Node.JS TCP Sockets or Google Chrome Sockets can be trivially implemented.
When is this feature?
You may provide guidance so that I can implement this transport?
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
No files or tests are named. Start by reviewing socket.io's transport architecture and the Node.js TCP Sockets and Google Chrome Sockets references mentioned in the issue, then ask maintainers to define the transport's scope and acceptance criteria before implementation.
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