[
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15681320#comment-15681320
]
James E. King, III commented on THRIFT-3979:
--------------------------------------------
I would like to propose that:
# There is no need for an additional protocol as originally described.
# Agree the original ask is to provide a way for thrift to uniquely identify a
client across any transport (including stateless ones).
# Standardize on a mechanism to satisfy item #2 and make it part of the core
(meaning it needs to be implemented in every language).
I haven't looked at how THeader works. Is there a description of how it
obtains and sustains a session ID per unique client across any transport? Does
one need to use contrib//fbthrift with it (the related thrift ticket mentions
fbthrift a few times)?
> 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)
