FastCGI: 30 Years Old and Still the Better Protocol for Reverse Proxies

1. libwas

   1 1 18 - C++

   The Web Application Socket (WAS) protocol and reference implementation

   

   I agree with the article, FastCGI is better than HTTP for these things.

   Though I'd like to make another protocol known: Web Application Socket (WAS). I designed it 16 years ago at my dayjob because I thought FastCGI still wasn't good enough.

   Instead of packing bulk data inside frames on the main socket, WAS has a control socket plus two pipes (raw request+response body). Both the WAS application and the web server can use splice() to operate on a pipe, for example. No framing needed. Also, requests are cancellable and the three file descriptors can always be recovered.

   Over the years, we used WAS for many of our internal applications, and for our web hosting environment, I even wrote a PHP SAPI for WAS. Quite a large number of web sites operate with WAS internally.

   It's all open source:

   - library: https://github.com/CM4all/libwas

2. SaaSHub

   www.saashub.com sponsored

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. libcommon

   2 3 25 9.7 C++

   Library of reusable C++ code

   

4. beng-proxy

   3 1 40 9.7 C++

   Web server

   

5. davos

   4 1 1 - C++

   WebDAV server (by CM4all)

   

6. php-src

   5 1 3 0.0 C

   A PHP fork with WAS support (https://github.com/CM4all/libwas) (by CM4all)

   

7. Mercure

   6 25 5,296 9.4 Go

   🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications

   

   That can be used with https://mercure.rocks :)

Suggest a related project