>From reading the Thrift Paper and looking at the source it appears as though Thrift doesn't support Bi-Directional RPC calls. I have an application which functions as a server and 90% of the time the clients will be calling RPC functions via Thrift like any other Thrift app.
My problem is periodically the server needs to push a notification to the client by effectively calling an RPC function on the client. My app needs the clients to pick these notifications up fairly quickly but they may only happen every few hours so its not practical to have the clients poll the server every 10 seconds or so. >From looking at the code and documentation it seems that I should be able to effectively run the client and server methods on both ends of the connection. Then I could implement my own transport to send the traffic to the correct client or server methods depending on which the traffic belongs to. Is this feasible, or have a missed something about the design of Thrift? Has anyone else done this before? Thanks, Charlie M
