3 ms·
Isn't this just CGI, straight out of the 90s, but with a needless cycle through JSON?
by nly 11y ago
Isn't this just CGI, straight out of the 90s, but with a needless cycle through JSON?
- deforciant 11y agoapparently middleware (cgi) is just an additional feature here
- sdegutis 11y agoCorrect.
- 5h 11y agoThat's kind of what i was thinking - somewhere between good ol' cgi and a reverse proxy .... Unfortunate because I'm semi-looking for a simple service that will let me configure a stateful new frontend to an old API - title made me think it might be along those lines.
- rakoo 11y agoThere's a huge difference: CGI is the ultimate backend in the HTTP stack, while this allows you to run scripts as middleware (ie modifying the response headers/body based on previous processing)
- bmurphy1976 11y agoNot necessarily true. CGI could shell out to other CGI code if it wanted to. Turtles all the way down.
- rakoo 11y agoWhat if the backend is not CGI ? What if I want to use a script to gzip the output of a backend that doesn't compress anything ? Of course you can just call that backend through HTTP, but then you add another huge dependency on your little script that should just be as simple as "gzip -c -"