My understanding is that Thrift over HTTP hinders some of the strengths in native Thrift. Simplicity, ability to support encryption, compression, NIO and persistent connections just to name a few. But yes, being able to have the server behind HTTPD is on the plus side.
Danushka On Thu, Jul 3, 2014 at 12:16 AM, Marlon Pierce <[email protected]> wrote: > I'm curious if anyone has looked into running Thrift over HTTP. We are > using TThreadPoolServer for the server and TServerSocket for transport in > AiravataAPIServer.java, but we're being encouraged to look into HTTP > bindings for publicly distributed SDKs. > > Using HTTP would allow us to put the server behind an Apache HTTPD server > (for example) and to take advantage of lots of existing protocol > implementations. > > Marlon > >
