Java client API

Hec H hec0101 at
Thu Mar 24 16:51:01 EDT 2011

Really cool to see general thoughts on java driver. Non related: +1 Jetty driver 
- pretty granular api behavior plus intuitive interface. Also Stringtree offers 
a flawless mapping of hashmap - json and seems pretty flexible.

From: Russell Brown <russell.brown at>
To: Sean Cribbs <sean at>
Cc: riak-users at
Sent: Thu, 24 March, 2011 15:43:50
Subject: Re: Java client API

On 24 Mar 2011, at 14:15, Sean Cribbs wrote:

>>> Likewise, I'd like to suggest RiakDoc
>> I can see why but I think that might be too specific, not every entry in riak 
>>is a document (but every document in riak is an entry.)
> I understand the desire to have a better name for what you're storing in Riak 
>(I went down that road myself in the Ruby client for a while), but for 
>consistency's sake it makes most sense to use "object" over "entry" or "doc". 
>Using something else just invites confusion when someone reads the wiki and 
>other documentation and then tries to apply what they learned to a specific 
>language driver.

Oh yeah. I had not even considered that. A strong enough reason to settle it 
(for me at least.)

> That said, there's no reason you can't build abstractions over the top of the 
>object that are documents, entries, blobs, etc.
> "RObject" is the class name the Ruby client uses, for what it's worth.
> Sean Cribbs <sean at>
> Developer Advocate
> Basho Technologies, Inc.
> _______________________________________________
> riak-users mailing list
> riak-users at

riak-users mailing list
riak-users at

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the riak-users mailing list