httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Eissing <stefan.eiss...@greenbytes.de>
Subject Re: drop experimental from http2 for 2.4.next?
Date Mon, 17 Apr 2017 08:24:54 GMT
These modules, they grow up so fast...

For the project, it would be good to drop that "experimental" and 
treat HTTP/2 as an integral part of httpd. Not only for political
posturing (which is important), but also for very technical reasons.

Looking at https://w3techs.com/technologies/details/ce-http2/all/all
one can see that HTTP/2 is used by 13% of all sites, which is almost
double from 1 year ago. Firefox telemetry reports HTTP/2.0 now 
on 35% of all responses received.

What needs to be done? From what I saw in the last two years, these 
are key areas to improve:

  1. separation of semantics and serialisation
  2. connections with >1 requests simultaneously

mod_http need to spin off a mod_http1 with the parts that read
and write headers, handle chunked encoding in requests
and responses. etc.

mpm needs facilities for processing slave connections and assign
its resources to slave/master connections in fair and performant
ways.

As much as I like to work on it, I am certainly not able to do
that by myself. So, yes, I welcome getting rid of experimental.

Cheers,

-Stefan


> Am 16.04.2017 um 15:00 schrieb Jim Jagielski <jim@jaguNET.com>:
> 
> Agreed. The "tag" is being used to keep it out of distros
> as well as to continue the FUD that httpd doesn't "really"
> support http/2.
> 
>> On Apr 15, 2017, at 5:02 PM, Eric Covener <covener@gmail.com> wrote:
>> 
>> Hi everyone, shall we drop experimental from mod_http2 for 2.4.next?
>> 
>> We could drop it and keep CTR.
>> 
>> -- 
>> Eric Covener
>> covener@gmail.com
> 


Mime
View raw message