[
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15681420#comment-15681420
]
Jens Geyer edited comment on THRIFT-3979 at 11/20/16 4:42 PM:
--------------------------------------------------------------
You need /some/ piece of information. Whether one calls it state, session,
header value, ID or something else and under which name it is sent over the
wire is completely irrelevant. The only benefit with standardized meta headers
is that they do not require some routing mechanism in between to understand the
entire message, only the header part must be understand. However, per today all
Thrift all existing server implementations do not even try to use headers this
way (if headers are supported at all).
was (Author: jensg):
You need some piece of information. Whether one calls it state, session, header
value, ID or something else and under which name it is sent over the wire is
completely irrelevant. The only benefit with meta headers is that they do not
require some routing mechanism in between to understand the entire message,
only the header part must be understand. However, per today all Thrift all
existing server implementations do not even try to use headers this way (if
headers are supported at all).
> 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
>
> Sometimes, customers wanna put some options (username, password, id, etc.) 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)
