[ https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15694156#comment-15694156 ]
Jens Geyer commented on THRIFT-3979: ------------------------------------ Yeah, there are a lot of possible scenarios and I really doubt that we can prove the one-fits-all solution. Thrift to my understanding is a toolkit, that provides a bunch of options, but otherwise tries to get out of the way as much as possible. > 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)