What deficiencies of http://www.reversehttp.net/ is this trying to solve?
I've been happy with the reliability of reversehttp for all the testing I've done with it.
If you're using ruby, hookout does a great job running your rack app as a reversehttp endpoint: http://github.com/paulj/hookout