From: Thomas Hurst <tom.hurst@...>
Date: 2008-01-15T00:46:09+09:00
Subject: Re: [ANN] Thin v0.5.2 Cheezburger released

* Francis Cianfrocca (garbagecat10@gmail.com) wrote:

> EventMachine doesn't currently support forking after starting up TCP
> listeners, but that's mostly because it can't be requested with the
> current Ruby glue. (There's also a minor issue with CLOEXEC on Unix
> platforms.) We're working on some significant API changes in
> EventMachine that in fact will allow preforking among many other
> things.

Excellent, thanks.

> The usual issue with preforking is that it doesn't work well on every
> platform. From the light testing I've done myself, it's reasonably
> fair on Linux. It's not good at all on Windows, unless they've changed
> something since the last time I tested it. What's your experience
> been?

I have next to no experience with Ruby on Windows; I don't think it
really matters.  Nobody who matters deploys live applications on it, and
those poor deranged people who do can make do without the capability
just as they do now.

On OS's that don't support concurrent accept()s you can just do what a
preforking Apache does on those systems; use a lockfile.  I'm quite sure
no OS is going to be getting away with breaking that.

-- 
Thomas 'Freaky' Hurst
    http://hur.st/