On 27 Sep 2015, at 8:41 PM, Graham Leggett <[email protected]> wrote: > I think I have cracked the async problem for both request and connection > output filters with this patch.
Well, cracked the async problem for all file buckets and non-morphing buckets, morphing buckets will currently still be flushed. The solution to that seems to be to try keep a morphing bucket from reaching the connection filters. A morphing bucket can safely be set aside in a request filter without any problems with pools. If a filter existed at the end of the request filters that detected morphing buckets and read them before sending them downstream, that filter could safely set aside the rest of the morphing bucket without being forced to read the whole thing in (and thus block). If the filter received a flush the whole thing gets sent and we block, but that’s what flush means so that’s fine. Patch to follow. Regards, Graham —
