On Wed, Nov 23, 2011 at 6:02 PM, Graham Dumpleton
<graham.dumple...@gmail.com> wrote:
> On 24 November 2011 01:38, Rodrigo Campos <rodrig...@gmail.com> wrote:
>> On Mon, Nov 21, 2011 at 12:55 PM, Rodrigo Campos <rodrig...@gmail.com> wrote:
>>> On Mon, Nov 21, 2011 at 3:07 AM, Graham Dumpleton
>>> <graham.dumple...@gmail.com> wrote:
>>>> On 20 November 2011 14:08, Rodrigo Campos <rodrig...@gmail.com> wrote:
>>>>
>>>> In mod_wsgi 4.0 those concepts are properly separated. The
>>>> inactivity-timeout is only for case where process is completely idle,
>>>> no active requests at all.
>>>
>>> Is there any estimated date when mod_wsgi 4.0 will be released ?
>>> Is it too risky to try to compile todays trunk and use it in
>>> production (previous sevral days on testing) ? Are there any "blocker"
>>> issue you are aware of ?
>>
>> Sorry to bother you again. But was this question lost ? If you didn't
>> answer because you are too busy, no problem. Please take your time.
>> But I wanted to make sure it wasn't lost :)
>
> It wasn't lost, I did see it. I just don't have a good answer right now.

=)

>
> I would like to get mod_wsgi 4.0 out soon as Apache people are getting
> closer to Apache 2.4 being released and so need to have it out before
> then as mod_wsgi 3.3 is not compatible with Apache 2.4.

Ohh, I see.

>
> There are a number of things to be done before can release mod_wsgi
> 4.0. These are:
>
> 1. Validate compiles against last Python 3.3 trunk.
> 2. Solve Python library linking issues with Python 3.2+.
>
> Also ideally:
>
> 3. Changes to New Relic configuration directives. (Not happy with how done 
> now).
> 4. Changes to New Relic statistics sampler. (Not happy with how done now).

Sound nice

>
> Despite above, the current mod_wsgi 4.0 trunk is stable. This version
> has got more testing than any prior version when being developed as I
> have for most of the past year had it sitting running load tests
> continuously with New Relic monitoring it so as to test New Relic
> Python agent. So, has got a good working out.

Great, good to know

>
> I guess I would like to have it out by the end of the year at the
> latest. The sooner the better though.

Great! I'll let you know how it works for us if we decide to compile
it from source




Thanks a lot!
Rodrigo

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to 
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to