You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (JIRA)" <ji...@apache.org> on 2016/11/22 23:15:58 UTC

[jira] [Closed] (THRIFT-3979) offer TExtendedBinaryProtocol for customers

     [ https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Geyer closed THRIFT-3979.
------------------------------
    Resolution: Won't Fix
      Assignee: Jens Geyer

Closed as WONTFIX, the recommended solution is to use {{THeader}} instead. As aside effect, this should help with making {{THeader}} available with more languages. 

Yes, we want your {{THeader}} patch! :-)

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