While this is a question that would fit better on the Java driver group
[1], I'll try to provide a very short answer:
1. Cluster is an long-lived object and the application should have only 1
instance
2. Session is also a long-lived object and you should try to have 1 Session
per keyspace.
A
you would create a new session. Don't create a new cluster, that will
quickly exhaust the connections to the servers
On Fri, Mar 7, 2014 at 3:42 PM, Green, John M (HP Education) <
john.gr...@hp.com> wrote:
> I've been tinkering with both the C++ and Java drivers but in neither
> case have I got
I've been tinkering with both the C++ and Java drivers but in neither case have
I got a good indication of how threading and resource mgmt should be
implemented in a long-lived multi-threaded application server process.That
is, what should be the scope of a builder, a cluster, session, and s
