thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoshuang LU (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (THRIFT-3979) offer TExtendedBinaryProtocol for customers
Date Mon, 21 Nov 2016 07:33:58 GMT

    [ https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682784#comment-15682784
] 

Xiaoshuang LU commented on THRIFT-3979:
---------------------------------------

Hi [~jking], Jens has already told me that THeader can be used for customers' options. And
I proposed TExtendedBinaryProtocol before I knew THeader.

It seems that my old description is a litter bit confusing and makes you think what I want
is security functionalities. So I just explain my solution more precisely.

Thanks.

> 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 (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)

Mime
View raw message