I don't think this needs a formal vote, but I'll give it the
weekend, for people to chime in...
On Fri, Sep 25, 2015 at 3:53 PM, Greg Stein wrote:
> IMO, call it experimental, and detail what that means in the release notes
> or an FAQ on the site.
+1
--
Eric Covener
cove...@gmail.com
On Fri, Sep 25, 2015 at 11:51 AM, Rainer Jung
wrote:
> Am 25.09.2015 um 17:56 schrieb Plüm, Rüdiger, Vodafone Group:
>
>> ...
>>> +1 on CTR for mod_h2 in 2.4.x
>>>
>>>
>> Just to clarify: CTR only on the code in modules/http2. All changes /
>> adjustments that might be needed to mod_ssl should st
/config.m4)
-Ursprüngliche Nachricht-
Von: Jim Jagielski [mailto:j...@jagunet.com]
Gesendet: Freitag, 25. September 2015 17:46
An: dev@httpd.apache.org
Betreff: Re: mod_h2 CTR (Was: Re: svn commit: r1705257 -
/httpd/httpd/trunk/modules/http2/config.m4)
In any case, let's not bike-shed on
>
> Just to clarify: CTR only on the code in modules/http2. All changes /
> adjustments that might be needed to mod_ssl should stay RTC.
>
Yes.
/config.m4)
-Ursprüngliche Nachricht-
Von: Jim Jagielski [mailto:j...@jagunet.com]
Gesendet: Freitag, 25. September 2015 17:46
An: dev@httpd.apache.org
Betreff: Re: mod_h2 CTR (Was: Re: svn commit: r1705257 -
/httpd/httpd/trunk/modules/http2/config.m4)
In any case, let's not bike-shed on
> -Ursprüngliche Nachricht-
> Von: Plüm, Rüdiger, Vodafone Group
> Gesendet: Freitag, 25. September 2015 17:51
> An: dev@httpd.apache.org
> Betreff: AW: mod_h2 CTR (Was: Re: svn commit: r1705257 -
> /httpd/httpd/trunk/modules/http2/config.m4)
>
>
>
>
> -Ursprüngliche Nachricht-
> Von: Jim Jagielski [mailto:j...@jagunet.com]
> Gesendet: Freitag, 25. September 2015 17:46
> An: dev@httpd.apache.org
> Betreff: Re: mod_h2 CTR (Was: Re: svn commit: r1705257 -
> /httpd/httpd/trunk/modules/http2/config.m4)
>
> In
In any case, let's not bike-shed on what we call it, or whatever...
Let's focus on deciding if we are cool with it being CTR once it's
folded into 2.4.x and "handling" it as we do mod_lua.
> On Sep 25, 2015, at 11:09 AM, Eric Covener wrote:
>
> On Fri, Sep 25, 2015 at 11:06 AM, Yann Ylavic wrote:
>> On Fri, Sep 25, 2015 at 4:31 PM, Jim Jagielski wrote:
>>> I'd like to propose that we consider mod_h2 in 2.4.x as CTR and
>>> in the same category as mod_lua... That is, somewhat "pr
> Am 25.09.2015 um 17:09 schrieb Eric Covener :
>
> On Fri, Sep 25, 2015 at 11:06 AM, Yann Ylavic wrote:
>> On Fri, Sep 25, 2015 at 4:31 PM, Jim Jagielski wrote:
>>> I'd like to propose that we consider mod_h2 in 2.4.x as CTR and
>>> in the same category as mod_lua... That is, somewhat "prod-ex
On Fri, Sep 25, 2015 at 5:09 PM, Eric Covener wrote:
> On Fri, Sep 25, 2015 at 11:06 AM, Yann Ylavic wrote:
>> On Fri, Sep 25, 2015 at 4:31 PM, Jim Jagielski wrote:
>>> I'd like to propose that we consider mod_h2 in 2.4.x as CTR and
>>> in the same category as mod_lua... That is, somewhat "prod-
On Fri, Sep 25, 2015 at 11:06 AM, Yann Ylavic wrote:
> On Fri, Sep 25, 2015 at 4:31 PM, Jim Jagielski wrote:
>> I'd like to propose that we consider mod_h2 in 2.4.x as CTR and
>> in the same category as mod_lua... That is, somewhat "prod-experimental"
>> in that some features may still change, bu
On Fri, Sep 25, 2015 at 4:31 PM, Jim Jagielski wrote:
> I'd like to propose that we consider mod_h2 in 2.4.x as CTR and
> in the same category as mod_lua... That is, somewhat "prod-experimental"
> in that some features may still change, but stable enough to be
> usable in production environs.
I l
I'd like to propose that we consider mod_h2 in 2.4.x as CTR and
in the same category as mod_lua... That is, somewhat "prod-experimental"
in that some features may still change, but stable enough to be
usable in production environs.
> On Sep 25, 2015, at 9:14 AM, Yann Ylavic wrote:
>
> On Fri, Sep 25, 2015 at 2:42 PM, Jim Jagielski wrote:
>>
>>> On Sep 25, 2015, at 6:41 AM, Stefan Eissing
>>> wrote:
>>>
>>>
Am 25.09.2015 um 12:32 schrieb Yann Ylavic :
On Fri, Sep 25, 2015 at 11:58 AM, Stefan Eissing
>>
On Fri, Sep 25, 2015 at 9:14 AM, Yann Ylavic wrote:
> What should be the name of the module? http2_module/mod_http2 or as
> currently h2_module/mod_h2?
I'm personally fine with status quo of h2.
On Fri, Sep 25, 2015 at 2:42 PM, Jim Jagielski wrote:
>
>> On Sep 25, 2015, at 6:41 AM, Stefan Eissing
>> wrote:
>>
>>
>>> Am 25.09.2015 um 12:32 schrieb Yann Ylavic :
>>>
>>> On Fri, Sep 25, 2015 at 11:58 AM, Stefan Eissing
>>> wrote:
I see. And rename the configuration options and d
> On Sep 25, 2015, at 6:41 AM, Stefan Eissing
> wrote:
>
>
>> Am 25.09.2015 um 12:32 schrieb Yann Ylavic :
>>
>> On Fri, Sep 25, 2015 at 11:58 AM, Stefan Eissing
>> wrote:
>>>
>>> I see. And rename the configuration options and documentation, while we are
>>> at it...
>>
>> Note that I'm
On Fri, Sep 25, 2015 at 12:41 PM, Stefan Eissing
wrote:
>
>> Am 25.09.2015 um 12:32 schrieb Yann Ylavic :
>>
>> On Fri, Sep 25, 2015 at 11:58 AM, Stefan Eissing
>> wrote:
>>>
>>> I see. And rename the configuration options and documentation, while we are
>>> at it...
>>
>> Note that I'm *not* ag
> Am 25.09.2015 um 12:32 schrieb Yann Ylavic :
>
> On Fri, Sep 25, 2015 at 11:58 AM, Stefan Eissing
> wrote:
>>
>> I see. And rename the configuration options and documentation, while we are
>> at it...
>
> Note that I'm *not* against the name being h2!
Yann, I know. And I do not want to say
On Fri, Sep 25, 2015 at 11:58 AM, Stefan Eissing
wrote:
>
>> Am 25.09.2015 um 11:40 schrieb Yann Ylavic :
>>
>> On Fri, Sep 25, 2015 at 11:31 AM, Stefan Eissing
>> wrote:
>>>
APACHE_MODULE(h2,
>>>
>>> since there is no modules named "http2"?
>>
>> --enable-http2=x sets enable_http2=x, so we
> Am 25.09.2015 um 11:40 schrieb Yann Ylavic :
>
> On Fri, Sep 25, 2015 at 11:31 AM, Stefan Eissing
> wrote:
>>
>>> APACHE_MODULE(h2,
>>
>> since there is no modules named "http2"?
>
> --enable-http2=x sets enable_http2=x, so we force enable_http2=no if
> --enable-http2 isn't used, like we fo
On Fri, Sep 25, 2015 at 11:31 AM, Stefan Eissing
wrote:
>
>> APACHE_MODULE(h2,
>
> since there is no modules named "http2"?
--enable-http2=x sets enable_http2=x, so we force enable_http2=no if
--enable-http2 isn't used, like we force enable_h2=no wrt enable-h2.
Btw, whatever --enable-h[ttp]2 is
Ah, understood. Thanks!
But would it then not make more sense to have both --enable-* do:
> APACHE_MODULE(h2,
since there is no modules named "http2"?
> Am 25.09.2015 um 11:23 schrieb Ruediger Pluem :
>
>
>
> On 09/25/2015 10:58 AM, Stefan Eissing wrote:
>> Me not fully understand. Why at al
On 09/25/2015 10:58 AM, Stefan Eissing wrote:
> Me not fully understand. Why at all and why only there? (curiousity)
Because it tries to build mod_h2 even if nghttp2 is not present.
Because
APACHE_MODULE(http2,
and
APACHE_MODULE(h2,
effectively setup two distinct modules with the same objec
Me not fully understand. Why at all and why only there? (curiousity)
> Am 25.09.2015 um 10:54 schrieb rpl...@apache.org:
>
> Author: rpluem
> Date: Fri Sep 25 08:54:38 2015
> New Revision: 1705257
>
> URL: http://svn.apache.org/viewvc?rev=1705257&view=rev
> Log:
> * Disable the http2 modules if
27 matches
Mail list logo
