Skip to content
Commits on Jun 21, 2012
  1. Adds 0.8 compatibility

    Hopefully .fork() behavior, new exit event and new kill() name are the only changes that matter.
Commits on Apr 30, 2012
  1. Lints some code lines

Commits on Feb 28, 2012
  1. Merge pull request #2 from robmerrell/master

    workers not restarting correctly if only 2 fail within monitor's frequency
  2. @robmerrell

    Update package.json

    robmerrell committed
  3. removed clearTimeout in workerEnd who was causing worker-error in cas…

    Rob Merrell committed
    …es that it shouldn't
Commits on Dec 16, 2011
Commits on Dec 15, 2011
  1. Merge pull request #1 from oleics/master

    Fixed main field of package.json
  2. @oleics

    Fixed main field of package.json

    oleics committed
  3. Change Rack.start() to accept a number as the total workers to launch

    and a callback to run as the master (instead of listenning for
    "master-start"). Both parameters are optional and can be used in any
    Also, change Rack.worker() to have a string parameter as the (relative)
    path to a node file to run as worker. This way you also don't have to
    listen for the "worker-start" event.
    Check require.js example.
  4. Fix typo in messages.js example

Commits on Dec 14, 2011
  1. Add rack.restart(interval[, cb ])

    Interval (in ms) is the time between every worker.kill(SIGTERM) that
    is called. If you specify a callback, it will trigger when every
    worker has been killed (and a new one started).
  2. Add rack.monitor(max, freq); add monitor.js example

    Before calling rack.start() you can call rack.monitor()
    like this:
        rack.monitor(1, 60000);
    This means 1 worker can die every minute (60 secs) and
    it will restart (a new fresh worker). If the maximum
    death count is passed in that period, a "worker-error"
    event is triggered (check example).
  3. initial commit

Something went wrong with that request. Please try again.