mcollina / mcollina/socket.io-adapters
current status
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hey @mcollina where are you at right now? I have a project Sails.js which maintains adapters for different storage adapters for main app databases, but I really want to be able to use those same adapters to plug into Socket.io. I'd love to sync up on our adapter convention some time.
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
No source files, tests, or implementation entry points are named. First clarify the proposed adapter convention between Sails.js storage adapters and Socket.io, then compare it with the repository's Redis, AMQP (RabbitMQ), and MQTT adapter implementations; done requires an agreed integration scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100