On Fri, Jun 19, 2015 at 10:03 AM, Eric Covener cove...@gmail.com wrote:
Maybe make MAX_REQUESTS_IN_PIPELINE configurable and use 1 in your case?
that's interesting, will check it out.
This turned into a bot of a pain when I realized just using a flush
bucket accomplishes the same thing
-Ursprüngliche Nachricht-
Von: Eric Covener [mailto:cove...@gmail.com]
Gesendet: Dienstag, 30. Juni 2015 20:09
An: Apache HTTP Server Development List
Betreff: Re: option to block async write completion?
On Fri, Jun 19, 2015 at 10:03 AM, Eric Covener cove...@gmail.com
wrote
On Tue, Jun 30, 2015 at 8:53 PM, Plüm, Rüdiger, Vodafone Group
ruediger.pl...@vodafone.com wrote:
-Ursprüngliche Nachricht-
Von: Eric Covener [mailto:cove...@gmail.com]
Gesendet: Dienstag, 30. Juni 2015 20:09
An: Apache HTTP Server Development List
Betreff: Re: option to block async
On Tue, Jun 30, 2015 at 5:29 PM, Graham Leggett minf...@sharp.fm wrote:
To be 100% safe, send the flush bucket down the stack on it’s own, not tacked
onto the end of the brigade with the EOS.
Thanks all -- I lucked into having that relationship already between
the heap buckets and EOS, and the
On 30 Jun 2015, at 8:53 PM, Plüm, Rüdiger, Vodafone Group
ruediger.pl...@vodafone.com wrote:
This turned into a bot of a pain when I realized just using a flush
bucket accomplishes the same thing (everything up to the flush bucket
is blocking)
Are you sure that works with every filter in
I have a proprietary module that uses a proprietary library. The
library needs an EOR cleanup that must run on the same thread as the
handler. During async write completion it will often happen on the
wrong thread.
There's already a path for forcing a blocking write of a particular
bucket, so it
On Fri, Jun 19, 2015 at 9:54 AM, Jeff Trawick traw...@gmail.com wrote:
Can ap_hook_{suspend_resume}_connection() allow you to remove that
requirement?
I don't think so -- at least not easily. It's effectively fopen() and
close() for a special kind of file (that's being served)
On Fri, Jun 19, 2015 at 10:02 AM, Yann Ylavic ylavic@gmail.com wrote:
Maybe make MAX_REQUESTS_IN_PIPELINE configurable and use 1 in your case?
that's interesting, will check it out.
On 06/19/2015 09:51 AM, Eric Covener wrote:
I have a proprietary module that uses a proprietary library. The
library needs an EOR cleanup that must run on the same thread as the
handler. During async write completion it will often happen on the
wrong thread.
Can
On 06/19/2015 09:54 AM, Jeff Trawick wrote:
On 06/19/2015 09:51 AM, Eric Covener wrote:
I have a proprietary module that uses a proprietary library. The
library needs an EOR cleanup that must run on the same thread as the
handler. During async write completion it will often happen on the
wrong
On Fri, Jun 19, 2015 at 3:51 PM, Eric Covener cove...@gmail.com wrote:
Thanks for any ideas.
Maybe make MAX_REQUESTS_IN_PIPELINE configurable and use 1 in your case?
11 matches
Mail list logo
