I was talking about the way ahead for HTTP/2 support in httpd.

Regarding it as no longer "experimental" helps, I hope, to make
better progress on this. There have been two aspects to "experimental"
in my mind:

 1. The "we do not guarantee that this is how it will stay". Anything
    may change in the next release to make it better and better.
 2. We try this out. It's an experiment. It may go away again.

Removing "experimental" makes it clear to everyone that the project
has been working on 1 and that http2 has become a core part of
httpd, similar to ssl. And as more than one person is working on
ssl, I hope that we will have more people working on http2.


> Am 16.05.2017 um 20:50 schrieb Eric Covener <cove...@gmail.com>:
> On Mon, Apr 17, 2017 at 4:24 AM, Stefan Eissing
> <stefan.eiss...@greenbytes.de> wrote:
>> 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.
> I'm sorry, but can you clarify the relationship between the initial
> bit and the welcoming of it not experimental?
> -- 
> Eric Covener
> cove...@gmail.com

Reply via email to