Thanks for the props! I detail my thoughts on h3 and httpd more below:
> Am 28.09.2019 um 00:18 schrieb William A Rowe Jr :
>
> On Fri, Sep 27, 2019 at 10:48 AM Eric Covener wrote:
> On Fri, Sep 27, 2019 at 11:20 AM Helmut K. C. Tessarek
> wrote:
> >
> > On 2019-09-27 03:00, Stefan Eissing
Il giorno sab 28 set 2019 alle ore 00:19 William A Rowe Jr
ha scritto:
>
> On Fri, Sep 27, 2019 at 10:48 AM Eric Covener wrote:
>>
>> On Fri, Sep 27, 2019 at 11:20 AM Helmut K. C. Tessarek
>> wrote:
>> >
>> > On 2019-09-27 03:00, Stefan Eissing wrote:
>> > > I know of no plans to implement
On Fri, Sep 27, 2019 at 10:48 AM Eric Covener wrote:
> On Fri, Sep 27, 2019 at 11:20 AM Helmut K. C. Tessarek
> wrote:
> >
> > On 2019-09-27 03:00, Stefan Eissing wrote:
> > > I know of no plans to implement HTTP/3 support in Apache httpd.
> >
> > I'm sorry, but this seems rather strange to me.
Although I should had made a few things clear, seems some good discussion
happened. Amongst the same lines:
When I asked about Apache, I should had stated HTTPD. There is a QUIC
implementation on Apache.org under ATS (Apache Traffic Server), a reverse
proxy, load balancer daemon. While
> I'm very grateful that Stefan took the initiative to get h2 into httpd.
+1
On 2019-09-27 11:47, Eric Covener wrote:
> I don't think market share is a big motivating factor for active contributors.
Maybe not, but I remember a discussion a while back on this list that had to
do with features vs stability, about market shares and why other web servers
are gaining.
>
> HTTPD is great and familiar to lots of people, but HTTPD'S age brings
> a lot of baggage. Lots of other great servers have much
> less baggage and currently have much more commercial interest and buzz.
For a short time my employer talked about "two-speed IT" to frame how
different products
On Fri, Sep 27, 2019 at 11:20 AM Helmut K. C. Tessarek
wrote:
>
> On 2019-09-27 03:00, Stefan Eissing wrote:
> > I know of no plans to implement HTTP/3 support in Apache httpd.
>
> I'm sorry, but this seems rather strange to me. So what's the idea behind this
> decision (or better said the lack
On 2019-09-27 10:40, William A Rowe Jr wrote:
> This answer \V/ (from Stefan) below. More explanation follows...
Thanks Bill, your explanation certainly helped to shed some light on this.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint =
On 2019-09-27 03:00, Stefan Eissing wrote:
> I know of no plans to implement HTTP/3 support in Apache httpd.
I'm sorry, but this seems rather strange to me. So what's the idea behind this
decision (or better said the lack of a plan)?
"Let's wait until other web servers implement it and wonder
This answer \V/ (from Stefan) below. More explanation follows...
The httpd project is entirely transparent. All development decisions occur
on the email
list you asked this question. Stefan himself stepped up to integrate
Tatsuhiro's nghttp2
implementation into httpd (very successfully) so we
I think there are plenty resources online where you can find an answer to your
question.
> Am 27.09.2019 um 09:18 schrieb Mark Blackman :
>
>
>> On 26 Sep 2019, at 18:54, Alex Hautequest wrote:
>>
>>
> On 26 Sep 2019, at 18:54, Alex Hautequest wrote:
>
> https://news.slashdot.org/story/19/09/26/1710239/cloudflare-google-chrome-and-firefox-add-http3-support
>
> With that, the obvious question: what about Apache?
What’s the incentive to add it?
- Mark
I know of no plans to implement HTTP/3 support in Apache httpd.
> Am 26.09.2019 um 19:54 schrieb Alex Hautequest :
>
> https://news.slashdot.org/story/19/09/26/1710239/cloudflare-google-chrome-and-firefox-add-http3-support
>
> With that, the obvious question: what about Apache?
https://news.slashdot.org/story/19/09/26/1710239/cloudflare-google-chrome-and-firefox-add-http3-support
With that, the obvious question: what about Apache?
15 matches
Mail list logo
