[ https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682294#comment-15682294 ]
Xiaoshuang LU edited comment on THRIFT-3979 at 11/21/16 2:42 AM: ----------------------------------------------------------------- [~jking], thanks for your detailed comments. In fact, TExtendedBinaryProtocol is meant to give customers ability to have whatever they want in requests and responses. I just use username and password as examples. I will revise the issue description. Again, thank you. was (Author: in-chief): [~jking] thanks for your detailed comments. In fact, TExtendedBinaryProtocol is meant to give customers ability to have whatever they want in requests and responses. I just use username and password as examples. I will revise the issue description. Again, thank you. > 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)