Virtualizing APIs with Go and Python

Re:Virtualizing APIs with Go and Python by rakoo on Friday December 11, 2015 @11:32AM (#10718017)

There'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)

[ Parent | on HN ]

Re:Virtualizing APIs with Go and Python by bmurphy1976 on Friday December 11, 2015 @02:06PM (#10719111)

Not necessarily true. CGI could shell out to other CGI code if it wanted to. Turtles all the way down.

[ Parent | on HN ]

Re:Virtualizing APIs with Go and Python by rakoo on Saturday December 12, 2015 @11:15AM (#10723169)

What 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 -"

[ Parent | on HN ]