Re: Mongrel 2.0

["Luis Lavena" <luislavena-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

On Mon, Nov 17, 2008 at 6:32 PM, Evan Weaver <evan-72XWLPH10WVXUHR/Jj/Uug@public.gmane.org> wrote:
> Hi Mongrels,
>
> I'm working on trunk and would like to change the following things and
> release it as a 2.0rc.
>
> - Timestamped logging
> - 1.9.1rc compatibility
> - Early PID drop
> - Error code instead of connection-close, as discussed earlier
> - Option to fork and run from a shared socket on Linux instead of queueing

Can you give more details on this?

> - Move to a Rack handler interface, and include backwards-compatible
> versions of the current ones

How this will overlap / affect / interfere Rack and it's own handler
for mongrel?

> - Eliminate gem_plugins
> - Other random bugfixes from off the trac and github
>

I'll really liek to have mongrel repository moved to git prior the
release, I lost track of all the branches and what is current the past
months...

> I'm unsure of what to do about mongrel_cluster. Do people still use
> that? Only for the --clean option? It would be nice if it could go
> away.
>
> At a later date, I would like to include optional ESI parsing to help
> people's dev environments.
>
> Please fuss at me if these are bad.
>

Most of thos looks good, but hearing more the details of some points
details will help me a bit.

For the record, I'm working on some rake helpers to ease the building
of all the gems and also cross compilation, with the goal that noone
needs me or Windows to be able to release gems for the platform.

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams