What I mean is, if you have client.rpc1() <block for rpc1 to finish>
it doesn't really matter if you can do client.rpc2() <block for rpc1, then rpc2> from another thread or not, since it's dumb. :) On Wed, Jul 15, 2009 at 7:41 PM, Ian Holsman<[email protected]> wrote: > > On 16/07/2009, at 10:35 AM, Jonathan Ellis wrote: > >> IIRC thrift makes no effort to generate threadsafe code. >> >> which makes sense in an rpc-oriented protocol really. > > hmm.. not really. you can have a webserver calling a thrift backend quite > easily, and then you would have 100+ threads all calling the same code. >> >> On Wed, Jul 15, 2009 at 7:25 PM, Joel Meyer<[email protected]> wrote: >>> >>> Hello, >>> Are there any recommendations on how to use Cassandra Clients in a >>> multi-threaded front-end application (java)? Is the Client thread-safe or >>> is >>> it best to do a client per thread (or object pool of some sort)? >>> Thanks, >>> Joel > > -- > Ian Holsman > [email protected] > > > >
