The generated cpp code for your interface will split up each method into send_methodName() and recv_methodName(). So, normally you'd use:
myServiceClientInstance->myMethod(...); but you could also do myServiceClientInstance->send_myMethod(...); // other things ret = myServiceClientInstance->recv_myMethod(); I've used this strategy to send a number of requests in parallel and then grab the results later. However, recv_* will still block. Anyone know if there's a better way to do this? On Mon, Jun 13, 2011 at 4:07 AM, 陈竞 <[email protected]> wrote: > I want to use asynchronous call . But it seems that thrift do not support > asynchronous call. > I need help. thanks > > -- > > celix >
