thanks Bryan. Can you elaborate little more on what you meant by using threads to achieve this? did you mean spawning multiple threads in ruby to get the data and coalescing them somehow?
thanks On Wed, Jan 11, 2012 at 3:05 PM, Bryan Duxbury <[email protected]> wrote: > I don't think we've implemented an async client in ruby thrift. > > The usual pattern is to use threads to achieve this sort of async behavior. > > On Thu, Jan 5, 2012 at 6:18 PM, T Vinod Gupta <[email protected]> > wrote: > > > does anyone know if thrift (0.6.0 or 0.8.0) support async/non-blocking > ruby > > client? if yes, how does the client get the return results? > > > > in my setup, the client calls the service with a request that can take > some > > time for the server to respond to. so how can this be made non-blocking > > wherein the client is gets notified with the results when the call really > > returns? > > > > thanks > > >
