[
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15680155#comment-15680155
]
James E. King, III commented on THRIFT-3979:
--------------------------------------------
How does one get access to the session ID for a given connected client from a
handler implementation? Assuming this is available then I agree with you, this
is something that could be provided outside thrift, if there is a correlating
session identifier. I have not seen a session identifier in the C++ runtime
server code. Perhaps you are talking about something available in another
language implementation like Java?
As for the original request here, the information suggested could be passed as
arguments to a thrift call instead of being handled "on the side". I think the
original intention however is to allow for session state to be carried from one
thrift call to the next. Your notion of providing a "SessionID" would be
sufficient to do this and if it's available now then I see no need to make this
enhancement.
> 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)
