Re: Mongrel 2.0

[Ezra Zygmuntowicz <ezmobius-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

	These all look good to me. If you move the --clean option into  
mongrel proper then we no longer need mongrel_cluster afaik.

Cheers-
-Ezra


On Nov 17, 2008, at 12:33 PM, Evan Weaver wrote:

> Also, I will document the release process.
>
> Evan
>
> On Mon, Nov 17, 2008 at 3: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
>> - Move to a Rack handler interface, and include backwards-compatible
>> versions of the current ones
>> - Eliminate gem_plugins
>> - Other random bugfixes from off the trac and github
>>
>> 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.
>>
>> Evan
>>
>> --
>> Evan Weaver
>>
>
>
>
> -- 
> Evan Weaver
> _______________________________________________
> Mongrel-development mailing list
> Mongrel-development-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
> http://rubyforge.org/mailman/listinfo/mongrel-development

Ezra Zygmuntowicz
ez-NLltGlunAUd/unjJdyJNww@public.gmane.org