[ https://issues.apache.org/jira/browse/THRIFT-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157503#comment-14157503 ]
Hudson commented on THRIFT-2704: -------------------------------- FAILURE: Integrated in Thrift-precommit #10 (See [https://builds.apache.org/job/Thrift-precommit/10/]) THRIFT-2704 generated oneway functions encode as T_CALL not T_ONEWAY (jensg: rev 61a4c96cf39a2b5472e437e3464153b605e5de4d) * compiler/cpp/src/generate/t_haxe_generator.cc > 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 > Assignee: Jens Geyer > > 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)