←back to thread

53 points heavensteeth | 1 comments | | HN request time: 0.412s | source
Show context
ryao ◴[] No.43652062[source]

  If you find yourself with a scripted language where processing HTTP requests might be too slow or unsafe, I can still see some utility for FastCGI. For most of the rest of us, HTTP won, just write little HTTP webservers.
Without serious development effort, I would expect using an existing web server with FastCGI is faster than writing your own web server. It is also more secure as the FastCGI application can be run as a different user in a chroot, or a namespace based sandbox like a docker container.
replies(4): >>43652278 #>>43652341 #>>43654110 #>>43671603 #
zokier ◴[] No.43652341[source]
Using HTTP does not preclude having a reverse proxy. So the only difference between FastCGI and HTTP is really what protocol your proxy and your application use, and I don't really see why FastCGI would be major win there.
replies(3): >>43655728 #>>43655779 #>>43655823 #
1. ◴[] No.43655728[source]