How to disable buffering when using FastCGI?
nicolas at gardentechno.com
Wed Oct 14 16:23:58 MSD 2009
2009/10/13 Maxim Dounin <mdounin at mdounin.ru>:
> On Tue, Oct 13, 2009 at 08:24:53PM +0200, Nicolas Grilly wrote:
>> It would be a perfect solution! If the fastcgi module is aware of
>> FastCGI record boundaries and stops buffering after having received a
>> full record, then the problem is solved. This gives to the FastCGI
>> backend complete control over the amount of buffering, sending short
>> records in order to limit buffering, or sending long records (around
>> 8KB) for normal buffering. Is it your plan for the future of the
>> upstream module?
> Complete control isn't really good thing, as it limits the ability
> to optimize brain-damaged backends. But as long as fastcgi
> finished record and not started another one - it's probably a good
> idea to pass data we got so far downstream. And current aproach
> won't work with keepalive connections anyway.
> But please keep in mind that I'm not Igor.
Thank you for your explanations! I will keep an eye on the evolution
of the FastCGI buffering, but I understand this is a complex topic. In
the meantime, I will use HTTP proxying.
More information about the nginx