From mboxrd@z Thu Jan 1 00:00:00 1970 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: =?UTF-8?B?U3TDqXBoYW5lIFJpdmnDqHJl?= Newsgroups: comp.lang.ada Subject: Re: Ada/GNAT/AWS-friendly web hosting Date: Sat, 14 Sep 2024 10:51:50 +0200 Organization: La Maison Message-ID: References: <20240913163315.7ec71431@tag.xn--rombobjrn-67a.se> Reply-To: stef@genesix.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 14 Sep 2024 10:51:51 +0200 (CEST) Injection-Info: dont-email.me; posting-host="8b831ad133baad0e80af0de91ddf01a9"; logging-data="1608809"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Rb3fmNrmPKCn4wBeRNOA5ONDbnGTcQRo=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:QR9E7frneSLOoHQt8TzajhYIbak= Content-Language: fr In-Reply-To: Xref: news.eternal-september.org comp.lang.ada:66379 List-Id: OK. Got it. Actually, it depends on the problem to be solved. In the case I mentioned (PHP websites), FastCGI is a must and the FastCGI cache a performance grall. FastCGI can be useful, even in Ada, if the site has to serve large quantities of static text and static images, that will make good use of a FastCGI cache. But for dynamic sites (without static datas) written without PHP, I agree that the WebSockets protocol is indeed ideal. WebSockets is a http1 only protocol. What doesn't matter. In most dynamic sites, such as business software, http2 or http3 are useless. -- Stéphane Rivière Ile d'Oléron - France