On Thu, 22 Oct 2020 20:52:27 +0200
José Miguel Sánchez García <soy.jmi2k_AT_gmail.com> wrote:
> Hello,
>
> I'm currently serving my static webpage with quark. I want to add some
> CGI, but the opinion here about CGI support in the server is pretty
> low. I'm trying to update the basecgi patch, but the latest changes
> adding interruptibility seem to complicate the design (the goals of
> these two are kinda opposite to what CGI does right? I mean, these are
> about memory-bounded operation and CGI scripts can generate
> arbitrarily long data, which must be known before even generating the
> response header). I have no experience with HTTP whatsoever, so I want
> to hear better-informed opinions ;)
Hi Jose,
I've recently had an idea that instead of adding support for running
scripts by HTTP server (which in any case leads to new fork() calls)
one could use a library providing HTTP server itself while all the
logic is created separately and is performed using callbacks from
library main loop. In that case one could attempt to handle dynamic
(and static using proper callbacks) content within fixed number of
threads.
--
Platon Ryzhikov <ihummer63_AT_yandex.ru>
Received on Sun Oct 25 2020 - 16:00:30 CET