Hi, Don't mean to hijack this thread, I have a similar question, is there a communication framework that can support reliable, full asynchronous,pipeline style data transfer?
Thanks! On Sun, Mar 13, 2011 at 7:29 AM, Ted Dunning <[email protected]> wrote: > For a more peer-based distributed system, you may want to establish servers > on both sides. > > But nothing prevents you from building a distributed system using Thrift. > > Can you explain your question a bit more? What characteristics did you > think might make Thrift unsuitable? What is lacking from RPC as a > primitive? > > On Sat, Mar 12, 2011 at 7:57 AM, Bryan Duxbury <[email protected]> wrote: > > > You can use Thrift to communicate between many nodes in a distributed > > system. It's still RPC - each node would have to host a server, and other > > nodes would have to make a connection to that server to pass information > > around. > > > > On Fri, Mar 11, 2011 at 10:06 PM, Joshua Partogi <[email protected] > > >wrote: > > > > > When talking about distributed system, Java has JMX and RMI. Is it > > > possible to build a distributed system, in a way multiple nodes can > > > talk to other nodes, with thrift? Or is thrift limited to RPC only. > > > > > > Sorry for the vague question. I am still evaluating thrift for > > > implementing the dynamo paper. > > > > > > -- > > > http://twitter.com/jpartogi > > > > > >
