Re: mod_proxy_http2 questions (was: [VOTE] backport mod_proxy_http2 to 2.4.x as experimental)

2016-03-11 Thread Yann Ylavic
On Fri, Mar 11, 2016 at 11:33 AM, Stefan Eissing wrote: > >> Am 10.03.2016 um 22:24 schrieb Yann Ylavic : >> >> [...] >>> >>> Concurrent Handling >>> --- >>> I was then thinking: how do I get all the concurrent proxy_http2

Re: mod_proxy_http2 questions (was: [VOTE] backport mod_proxy_http2 to 2.4.x as experimental)

2016-03-11 Thread Stefan Eissing
> Am 10.03.2016 um 22:24 schrieb Yann Ylavic : > > [...] >> >> Concurrent Handling >> --- >> I was then thinking: how do I get all the concurrent proxy_http2 requests to >> use the same connection? I was originally thinking about some dort of de-mux, >> a

Re: mod_proxy_http2 questions (was: [VOTE] backport mod_proxy_http2 to 2.4.x as experimental)

2016-03-10 Thread Yann Ylavic
On Thu, Mar 10, 2016 at 5:38 PM, Stefan Eissing wrote: > > Iterative, the Common Case > -- [] > > As to the input/output handling for that request_rec, that is basic mod_http2 > stuff. The core filters have been replaced with ones that shuffle

Re: mod_proxy_http2 questions (was: [VOTE] backport mod_proxy_http2 to 2.4.x as experimental)

2016-03-10 Thread Stefan Eissing
Hi Yann, thanks for the questions. I'd really love to bounce the idea of my implementation around here, because I hope that I got things right and, since I do not know all corners and hooks in our little product, to get feedback what I have overlooked. Iterative, the Common Case

mod_proxy_http2 questions (was: [VOTE] backport mod_proxy_http2 to 2.4.x as experimental)

2016-03-10 Thread Yann Ylavic
Hi Stefan, sorry I didn't look closely enough in mod_proxy_http2's code yet to answer the following questions by myself, so I'm asking here... On Wed, Mar 9, 2016 at 1:53 PM, Stefan Eissing wrote: > > When called inside a HTTP/1.1 connection, it will open/reuse >