On Tue, Jul 6, 2010 at 6:00 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > Because stateful keyspace is semantically closer to how people use it:
Hmm no other reason? Writing a client-side wrapper which turns get(key, column_path, clevel) into get(@keyspace, key, column_path, clevel) is trivial in pretty much any language. Well, looked at the code and switching isnt gonna be expensive so my concern is answered. Since set_keyspace resets login it might be "useful" to combine those two? set_keyspace(string, optional:auth)? Cheers, /thomas
