[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21093: Web server: response bodies systematically loaded in memory
From: |
Andy Wingo |
Subject: |
bug#21093: Web server: response bodies systematically loaded in memory |
Date: |
Fri, 24 Jun 2016 10:15:40 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
On Mon 20 Jul 2015 00:10, address@hidden (Ludovic Courtès) writes:
> The ‘sanitize-response’ procedure systematically loads the whole
> response body in memory, which causes obvious scalability issues (this
> is in 2.0.11.)
>
> In particular, when a request handler returns a port-taking procedure as
> its second return value, ‘sanitize-request’ will just call that
> procedure passing it a string output port.
>
> This procedure should instead be called from the server implementation’s
> ‘write’ hook, but that would necessitate an API change.
>
> Thoughts?
How would you set the Content-Length? Just leave it off and set
Connection: close ? Set it in the headers perhaps? Then you have to
verify later, which I dunno how nice that is. Maybe it is OK.
I would be happy to review patches :) Cc guile-devel.
Andy
- bug#21093: Web server: response bodies systematically loaded in memory,
Andy Wingo <=