[web-devel] [Yesod] Re: Better web app deployment

Michael Snoyman michael at snoyman.com
Mon May 7 07:03:09 CEST 2012


On Sun, May 6, 2012 at 5:51 PM, Douglas Livingstone <rampant at gmail.com> wrote:
> On 6 May 2012, at 11:00, web-devel-request at 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 at 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



More information about the web-devel mailing list