Dear Wiki user, You have subscribed to a wiki page or wiki category on "Thrift Wiki" for change notification.
The "ThriftIntegrationConventions" page has been changed by DavidReiss. http://wiki.apache.org/thrift/ThriftIntegrationConventions?action=diff&rev1=1&rev2=2 -------------------------------------------------- == HTTP == - - Thrift messages should be sent over HTTP/1.1 with Content-Length headers on both the request and response. + * Thrift messages should be sent over HTTP/1.1 with Content-Length headers on both the request and response. - - Thrift messages should be sent over HTTP POST. + * Thrift messages should be sent over HTTP POST. - - The request should be the POST body. No mime or url encoding should be used, just raw bytes. + * The request should be the POST body. No mime or url encoding should be used, just raw bytes. - - The response should be the HTTP response. Again, raw bytes. + * The response should be the HTTP response. Again, raw bytes. - - The Content-Type header for both request and response should be "application/x-thrift". + * The Content-Type header for both request and response should be "application/x-thrift". - - No framing should be used within either the request or response. + * No framing should be used within either the request or response. - - oneway requests should not be used over HTTP. + * oneway requests should not be used over HTTP. These conventions are followed by multiple HTTP classes in the Thrift source tree. == SSL == - - TODO + * TODO == SASL == - - TODO + * TODO == ZeroMQ == - - Normal Thrift calls should be made over REQ/REP sockets. + * Normal Thrift calls should be made over REQ/REP sockets. - - oneway requests can be made over PUSH/PULL or PUB/SUB sockets. + * oneway requests can be made over PUSH/PULL or PUB/SUB sockets. - - The request and response should be the entire content of the zmq message: no framing or encoding. + * The request and response should be the entire content of the zmq message: no framing or encoding. These conventions are followed by the patches at https://issues.apache.org/jira/browse/THRIFT-812 .
