I've always used socket-per-session. Socket-per-request will work, but it's going to waste a lot of time in TCP setup/teardown.
On Wed, Jul 8, 2009 at 4:32 PM, Viktor Klang<[email protected]> wrote: > On Wed, Jul 8, 2009 at 11:08 PM, Jonathan Ellis <[email protected]> wrote: > >> If an operation fails at the transport layer, reconnect? > > > I was more thinking along the lines of TSocket-connection pooling, one > socket per Session, one socket per request, one socket per unit-of-work, or > something else? > > Or is it better to be pragmatic and just go with Socket-per-request? > > >> >> >> On Wed, Jul 8, 2009 at 3:53 PM, Viktor Klang<[email protected]> >> wrote: >> > Hello guys, >> > >> > I'm toying with a Scala wrapper around the Cassandra Java API and I've >> tried >> > to plow thru most of the available documentation. >> > However, I will probably spam the list with questions, my current >> question >> > is: >> > >> > * What's the "best practice" when it comes to connection-management? >> > (TSocket) >> > > > > -- > Viktor Klang > Scala Loudmouth >
