Optimize Current base Module - Consider nginx

[crazy2be]

The base module right now uses an entirely homebrew solution (based on go) in order to achieve the effect of a reverse http proxy. Although it works reasonably well and is fairly reliable, the lack of optimization in both it and the go http methods that it uses means that under heavy loads it will use just as much (or even more!) CPU than the actual modules. A vanilla nginx and plugin-- or, if necessary, a fork/patch--should do the job much more efficiently. However, this not a particularly easy task, and it's not particularly important to the framework in this development stage, so this issue is low priority. Someone can feel free to take this on if they actually want to use this somewhere in production, or are more familiar with nginx.

[crazy2be]

It might be worthwhile to invest some time optimizing and cleaning up the code for the base module, as that should allow significant headway without having to throw away the use of go.