Closed Bug 730706 Opened 13 years ago Closed 13 years ago

kumascript: Build forking, robust server runner

Categories

(developer.mozilla.org Graveyard :: Editing, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lorchard, Unassigned)

References

Details

The HTTP service for kumascript is a JS module that can be run as a socket listener. That's not enough, though: It needs to be wrapped in a deployable server runner that will keep the service running through exceptions and errors, and can fork processes to take advantage of multiple CPU cores. This may need some IT consultation to determine what's the best arrangement for deployment.
Blocks: 730705, 659364
Blocks: 730704
Preempting some IT questions - the http service is served by node.js? Is it express? Are there existing node.js practices and tools for this?
The HTTP service is node, based on express, and there are many existing node practices and tools. Still working on picking the right one, though "up" [1] looks promising. There's also "forever" [2], but that doesn't handle forking off child processes. I'd probably need to DIY that with the new "cluster" support in node [3]. [1]: https://github.com/learnboost/up [2]: https://github.com/nodejitsu/forever [3]: http://nodejs.org/docs/v0.6.0/api/cluster.html
Version: MDN → unspecified
Component: Docs Platform → Editing
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.