From mboxrd@z Thu Jan 1 00:00:00 1970 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.ada Subject: Re: Ada/GNAT/AWS-friendly web hosting Date: Sat, 14 Sep 2024 07:26:04 -0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: <20240913163315.7ec71431@tag.xn--rombobjrn-67a.se> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 14 Sep 2024 09:26:04 +0200 (CEST) Injection-Info: dont-email.me; posting-host="f0b3208cd64aa384126f587d0af4cdfe"; logging-data="1432116"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+JrFCMM7OvMb5bwvrrJ4Zn" User-Agent: Pan/0.160 (Toresk; ) Cancel-Lock: sha1:QIj5gmVI02nm2cs6aAPVG5COZ6w= Xref: news.eternal-september.org comp.lang.ada:66377 List-Id: On Sat, 14 Sep 2024 09:01:32 +0200, Stéphane Rivière wrote: > We use FastCGI with Nginx to host tons of Wordpress web sites via > PHP_FPM. FastCGI allows us to implement an extremely high-performance > FastCGI cache. Caching is essential for slow and interpreted PHP > applications and/or high-traffic applications, whatever the language > used. I would use the server-side proxy approach. I see that FastCGI is basically an alternative to this, using a special protocol to communicate with the proxy, instead of just regular HTTP. But when I discovered that the “official website” (fastcgi.com) disappeared off the Web some years ago, I decided that the whole concept was becoming obsolescent and so best avoided. Also, it appears FastCGI doesn’t support WebSockets. Whereas server-side proxying does. Another point in favour of the latter.