[
https://issues.apache.org/jira/browse/THRIFT-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136162#comment-14136162
]
Jens Geyer commented on THRIFT-2704:
------------------------------------
This issue goes through the entire code. Similar issues do exist in next to all
code generators. Chances are that there is more to do with regard to the
different libraries implementations, similar to what you did with C++
> generated oneway functions encode as T_CALL not T_ONEWAY
> --------------------------------------------------------
>
> Key: THRIFT-2704
> URL: https://issues.apache.org/jira/browse/THRIFT-2704
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Compiler
> Affects Versions: 0.9.1
> Reporter: Konrad Grochowski
>
> Steven Varga wrote:
> {quote}
> Hi,
> the following service generates oneway RPC call flagged with T_CALL flag as
> opposed to expected T_ONEWAY; I need the T_ONEWAY flag to implement proper
> zero MQ message passing. Zero MQ message passing system differentiates
> between request - reply patterns and push - pull ones at socket level;
> Am I doing something wrong ?
> best,
> steve
> service foo {
> oneway void bar( 1:string value );
> }
> void fooClient::put( const std::string& value ) {
> send_bar( value ); // <- this is correct that recv_xxx is missing
> }
> // ----- incorrect or unreasoned T_CALL instead of T_ONEWAY
> void fooClient::send_bar(const std::string& value) {
> int32_t cseqid = 0;
> oprot_->writeMessageBegin("bar", ::apache::thrift::protocol::T_CALL,
> cseqid);
> ....
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
