Why though do most programming languages that have server-side rendering not do the extra step of fcgi? And basically listen to HTTP requests directly. Eg why can fpm not listen to http instead? What are the advantages of fpm listening to fcgi instead? > On 21 Mar 2021, at 15:39, Sam Hobbs <Sam@xxxxxxxxxxxxxxxxxx> wrote: > > HTML and FastCGI both require HTTP for the server and client to communicate. Server-side programming such as PHP require something like CGI, FastCGI or FPM to execute. CGI is the original technology, created for HTML to process forms. FastCGI is more efficient. I am not familiar with FPM but apparently it has improvements to FastCGI unique to PHP. > > > Gunter Grodotzki wrote on 3/21/2021 4:53 AM: >> Hi all, >> >> Why does fpm still use fcgi instead of http? What are the advantages (in modern days)? >> >> If it were to speak http, we could most probably avoid the requirement of nginx or similar as middlewoman, which makes cloud setups (docker, aws-alb, ...) a bit easier and more straight forward. >> >> What are the thoughts on this? Alternatively the built-in server but with forking capabilities (similar to fpm) :) >> >> Cheers, >> Gunter >> >
