Re: [web-devel] [Yesod] Re: Better web app deployment
On 6 May 2012, at 11:00, web-devel-request@haskell.org wrote:
I was actually very specific about what we should do: send an interrupt signal. In your case, you could catch that signal and allow your long-running processes to finish. Likewise, an app which is has any kind of long-running responses would want to take that approach.
All apps will need a variation on this, since even if the individual responses are fast, they will need to be completed before the process can exit. I'm not sure how this affects restarting Nginx, how does it handle pending responses when asked to restart with a new config? Douglas
On Sun, May 6, 2012 at 5:51 PM, Douglas Livingstone
On 6 May 2012, at 11:00, web-devel-request@haskell.org wrote:
I was actually very specific about what we should do: send an interrupt signal. In your case, you could catch that signal and allow your long-running processes to finish. Likewise, an app which is has any kind of long-running responses would want to take that approach.
All apps will need a variation on this, since even if the individual responses are fast, they will need to be completed before the process can exit. I'm not sure how this affects restarting Nginx, how does it handle pending responses when asked to restart with a new config?
Douglas
_______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel
I just tested this, and it works as we'd hope. Existing connections continue just fine, and new connections get routed to the new app process. Michael
participants (2)
-
Douglas Livingstone -
Michael Snoyman