Very nice! You mention that the connections are handled internally by Pelops, does that mean that potentially a different connection is used for each operation performed?
I had assumed using the same connection for several operations with ConsistencyLevel.ONE would provide a basic level of atomicity. For example, using the same connection for all operations in a web request would allow the request to read it's own writes. Is that assumption correct and does that impact on your decision to handle the connections internally to Pelops? Cheers, Dan On 13 June 2010 05:05, Ran Tavory <ran...@gmail.com> wrote: > Nice going, Dominic, having a clear API for cassandra is a big step forward > :) > Interestingly, at hector we came up with similar approach, just didn't find > the time for code that, as production systems keep me busy at nights as > well... We started with the implementation of BatchMutation, but the rest of > the API improvements are still TODO > Keep up the good work, competition keeps us healthy ;) > > > On Fri, Jun 11, 2010 at 4:41 PM, Dominic Williams < > thedwilli...@googlemail.com> wrote: > >> Pelops is a new high quality Java client library for Cassandra. >> >> It has a design that: >> * reveals the full power of Cassandra through an elegant "Mutator and >> Selector" paradigm >> * generates better, cleaner, less bug prone code >> * reduces the learning curve for new users >> * drives rapid application development >> * encapsulates advanced pooling algorithms >> >> An article introducing Pelops can be found at >> >> http://ria101.wordpress.com/2010/06/11/pelops-the-beautiful-cassandra-database-client-for-java/ >> >> Thanks for reading. >> Best, Dominic >> > >
