On Tuesday 11 November 2008 03:56:32 Mark Slee wrote: > This sounds reasonable to me and is probably how I would design such a > system. Thrift clients/servers are fundamentally unidirectional RPC, not a > bidirectional messaging system, so having a server on each end makes the > most sense. It sounds like what you really want here is asynchronous > messaging library, which isn't Thrift's primary intended purpose but can > certainly be accomplished.
Well, if you're using Python, you may want to take a look at txAMQP [1] It already implements asynchronous messaging using AMQP as the underlying transport. The idea is fairly simple, it simply wraps Thrift calls in an AMQP message. We plan to eventually release a Java port, but it should be pretty straightforward to port it to other languages. Cheers. 1 - http://launchpad.net/txamqp
