(I split these up, since answers touch on different topics):
> Am 21.10.2015 um 16:48 schrieb Graham Leggett :
>
> On 21 Oct 2015, at 4:18 PM, Stefan Eissing
> wrote:
>
>> How good does this mechanism work for mod_http2? On the one side it's
On 22 Oct 2015, at 6:04 PM, Stefan Eissing wrote:
>> mod_ssl already worries about buffering on it’s own, there is no need to
>> recreate this functionality. Was this not working?
>
> As I wrote "it has other bucket patterns", which do not get optimized by the
>
On 22 Oct 2015, at 6:03 PM, Stefan Eissing wrote:
> This is all true and correct - as long as all this happens in a single
> thread. If you have multiple threads and create sub pools for each from a
> main pool, each and every create and destroy of these
> Am 21.10.2015 um 16:48 schrieb Graham Leggett :
>
> On 21 Oct 2015, at 4:18 PM, Stefan Eissing
> wrote:
> [...]
>> 3. The amount of buffered bytes should be more flexible per stream and
>> redistribute a maximum for
>> the whole session
> Am 21.10.2015 um 16:48 schrieb Graham Leggett :
>
> On 21 Oct 2015, at 4:18 PM, Stefan Eissing
> wrote:
>
>> 7. The buckets passed down on the master connection are using another buffer
>> - when on https:// -
>> to influence the SSL record
> Am 21.10.2015 um 16:48 schrieb Graham Leggett :
>
> On 21 Oct 2015, at 4:18 PM, Stefan Eissing
> wrote:
>> 6. pool buckets are very tricky to optimize, as pool creation/destroy is not
>> thread-safe in general
>> and it depends on how the
On 22 Oct 2015, at 5:43 PM, Stefan Eissing wrote:
>> The blocking read breaks the spirit of the event MPM.
>>
>> In theory, as long as you enter the write completion state and then not
>> leave until your connection is done, this problem will go away.
>>
>> If
On 22 Oct 2015, at 5:55 PM, Stefan Eissing wrote:
>> With the async filters this flow control is now made available to every
>> filter in the ap_filter_setaside_brigade() function. When mod_http2 handles
>> async filters you’ll get this flow control for free.
>
>
On 21 Oct 2015, at 4:18 PM, Stefan Eissing wrote:
> How good does this mechanism work for mod_http2? On the one side it's the
> same, on the other quite different.
>
> On the real, main connection, the master connection, where the h2 session
> resides, things are
(Sorry for the long post. It was helpful for myself to write it. If this does
not
hold your interest long enough, just ignore it please.)
As I understand it - and that is incomplete - we have a usual request
processing like this:
A)
worker:
conn <--- cfilter <--- rfilter
10 matches
Mail list logo