Thrift doesn't provide a mechanism for this. If you want to do this communication in-process, you're going to need to navigate language extension models. You might be looking for a tool more like SWIG (http://www.swig.org).
What exactly is the criteria for running a "server" that you wish to avoid? Are you looking to avoid having a separate process? Avoid having ports open? You can configure Thrift to use local sockets rather than external interfaces -- for all intents and purposes, communication on the loopback interface is local. It'd also probably be possible to implement Thrift communication over shared memory, though personally I don't see a huge benefit if you're working with relatively small RPC messages, as opposed to large chunks of data that both processes operate on. This would still require two processes. Cheers, mcslee -----Original Message----- From: Skariah, Justin [mailto:[email protected]] Sent: Tuesday, November 23, 2010 5:24 AM To: [email protected] Subject: Calling local interface Hello Everyone, I went through some examples of thrift and saw how me can invoke remote interfaces implemented in another language it works really great. But I would love to call a local interface written in another language without running server or client. Is it possible?? If yes how much would be the dev effort required. Regards, Justin Skariah.
