Re: workers created when request comes in?

From: Eric Wong <normalperson@yhbt.net>
To: Joseph McDonald <superjoe@gmail.com>
Cc: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: workers created when request comes in?
Date: Tue, 15 Dec 2009 18:37:01 -0800	[thread overview]
Message-ID: <20091216023701.GA6398@dcvr.yhbt.net> (raw)
In-Reply-To: <73096a160912151737t48f6684fhbb5f047bc187c0eb@mail.gmail.com>

Joseph McDonald <superjoe@gmail.com> wrote:
> Is it possible to have unicorn spawn a new worker when a request comes
> in, and only allow that child to service the one request?
> 
> In development mode it would be nice if I could just save my changes
> and know that I will see them right away without having to HUP the
> server.

Hi Joseph,

Yes, just send SIGQUIT to yourself anywhere inside the application
dispatch and it'll defer the exit until your application is done
processing.

You should be able to just make it middleware like this:

  # name inspired by the "shotgun" gem
  class Unicorn::Shotgun < Struct.new(:app)
    def call(env)
      Process.kill(:QUIT, 0)
      app.call(env)
    end
  end

-- 
Eric Wong
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying