Greg Ames wrote:
Brian Pane wrote:
Looking at the pattern of calls to ap_core_output_filter() in the
event MPM, it occurred to me that it may be straightforward to hand
off the writing of the request to an async completion thread in a lot
of useful
real-world cases.
In function
Greg Ames wrote:
Brian Pane wrote:
I'm eager to hear some feedback on this idea:
* Will it work? Or am I overlooking some design flaw?
it should work as long as everything important that happens after the
check_pipeline_flush call still gets done somehow. a quick glance at
the code
Brian Pane wrote:
Looking at the pattern of calls to ap_core_output_filter() in the event
MPM, it occurred to me that it may be straightforward to hand off the
writing of the request to an async completion thread in a lot of useful
real-world cases.
In function check_pipeline_flush() in
Looking at the pattern of calls to ap_core_output_filter() in the
event MPM,
it occurred to me that it may be straightforward to hand off the
writing of the
request to an async completion thread in a lot of useful real-world
cases.
In function check_pipeline_flush() in http_request.c, a
