New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clustering / Multi-Core Server #37
Comments
Are you up for providing a PR? 😄 |
Sounds more like a plugin to me. We had to do some work on making stuff distributed recently too, so I think providing some help there would make sense. I'll read through the article but ideas are definitely welcome. |
It'd be the first :) I'm planning put a sample plugin repository up though (to also work on #22) and I'll let you know. |
Awesome, thanks! |
For those following this issue, please watch the feathers-cluster plugin. |
feathers-cluster has been tested and released to NPM. |
* bootstrap service filters * bump minor * add tests for filterMixin * missing test deps
* bootstrap service filters * bump minor * add tests for filterMixin * missing test deps
Runs semistandard on the actual generator code.
Fix old property name fallback for backwards compatibility
Check for params.provider in requireAuth hook
Fix old property name fallback for backwards compatibility
Check for params.provider in requireAuth hook
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs. |
Support for Cluster to create a multi-core Node.js server.
This could be a plugin for Feathers, or a built-in feature as is Socket.io and Primus.
Example of using Cluster:
Source http://adamnengland.wordpress.com/2013/01/30/node-js-cluster-with-socket-io-and-express-3/
The text was updated successfully, but these errors were encountered: