Am Montag, 5. August 2013, 09:57:16 schrieb Jim Jagielski: > On Aug 5, 2013, at 4:00 AM, Stefan Fritsch <s...@sfritsch.de> wrote: > > An ideal solution would put the buffering/decision for > > blocking/non-blocking into ap_pass_brigade(). This way other > > filters like deflate could also be called asynchronously. But I > > am not too optimistic that this can be achieved without API > > changes. > > Agreed, but from what I can see the proposed patch does > add some benefit, allows for future improvement, adds no > overhead and no bugs. As such, even though it doesn't completely > solve the whole issue, it is valuable enough to be folded into > 2.4. (imo 'natch)
It gives us a new API that we need to keep. But if you and Graham both think that this is a good tradeoff, then that's fine with me. But I want to test one more thing before I vote +1. Hopefully I will have some time for that next week-end. The wording of CHANGES and the docs need to be adjusted, though.
