[
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15688948#comment-15688948
]
Chris Simpson commented on THRIFT-3979:
---------------------------------------
That's assuming you maintain a persistent connection, which is easy for Socket
server/client transports but not for HTTP or other transport protocols.
We use HTTP server/client transports, and use Thrift on iOS, sending
credentials over the wire each time we create a connection is much less secure
than having a really long high entropy session token thats maintained between
connections. Also keep in mind that any THTTPTransport starts and ends its
connection lifecycle as far as the transport is concerned with each service
call and every flush, rather than when the client is instantiated, keep-alive
and other such things are usually handled under the hood and can be operated
upon but not universally unfortunately.
We also use AMQP transports, albeit internally where we don't need to pass
around this header data, but such transports don't even have the concept of a
"Connection" to the actual server (rather just a connection to the transport
AMQP server)
> offer TExtendedBinaryProtocol for customers
> -------------------------------------------
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
> Issue Type: Story
> Components: Wish List
> Affects Versions: 0.9.3
> Reporter: Xiaoshuang LU
> Assignee: Jens Geyer
>
> Sometimes, customers wanna put some options (whatever customers want) in each
> request and response. And these options ought to be transparent for
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra
> functionalities. I would like to propose the following solution to address
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
