I'm helping out with adding support for Rust in Thrift: https://github.com/maximg/thrift
I was working on adding an HTTP Transport, as this guide ( https://thrift.apache.org/docs/HowToNewLanguage) says it's one of the required transports if you want your language merged. After running into some bugs while implementing it, I took a look at some of the other implementations. The Python THttpServer doesn't send back the content-length, so using it with implementations like C++ break, as they rely on this content-length (my Rust implementation broke too). I fixed this on my local copy and ran into some more bugs, so I decided to try running the C++ THttpServer instead to make sure it wasn't some more weird python implementation bugs. However, I couldn't figure out how to run it, since it doesn't inherit from TServerTransport. I'm wondering now how necessary it is to implement this transport for a new language. I don't think I've ever seen it used, as it's slower than regular sockets and provides no benefit. I don't see any standard/documentation for this transport, so bugs like missing the content-length in the python implementation have popped up and make it not work with other languages. And finally I can't even figure out how to run it in C++, which makes it hard for me to develop my own implementation if I don't have a standard or a correct reference implementation to look at (although this might be an oversight on my part, please let me know if there's a way to run this). So in short, should the requirement to implement the HTTP transport for a new language be relaxed to just a recommendation (or even removed from the document altogether)? And if not, some help in getting the C++ implementation up and running would be appreciated.
