[THRIFT-2704] generated oneway functions encode as T_CALL not T_ONEWAY

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.1
• Component/s: C++ - Compiler
• Patch Info: Patch Available
• Assignee: Jens Geyer
• Reporter: Konrad Grochowski
• Created: 14/Sep/14 11:08
• Updated: 05/Nov/14 04:48
• Resolved: 17/Sep/14 21:01

Description

Steven Varga wrote:

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);
....
}

Issue Links

• relates to: THRIFT-2710 Smalltalk library does not support "oneway" message type
• relates to: THRIFT-2706 D library does not support "oneway" message type
• relates to: THRIFT-2707 Ruby library does not support "oneway" message type
• relates to: THRIFT-2708 Erlang library does not support "oneway" message type