Re: Clarifying "Read-before-Write"

2011-11-26 Thread Russell Brown
On 26 Nov 2011, at 01:14, Andres Jaan Tack wrote: > So I was just reading and thinking about this, and I don't understand the > advice offered under "Read-before-Write" at > http://wiki.basho.com/Client-Implementation-Guide.html. > > "Riak will return an encoded vector clock with every "fetch"

Re: Clarifying "Read-before-Write"

2011-11-26 Thread Andres Jaan Tack
Thanks! That explanation is perfect. I guess should have taken a look at some of the other clients as an example in the first place. Now I have something to fix for Riak-Cpp. :) -- Andres 2011/11/26 Russell Brown > > On 26 Nov 2011, at 01:14, Andres Jaan Tack wrote: > > So I was just reading a

Setting up a project on top of Riak

2011-11-26 Thread Mathieu D'Amours
Hi all, I'm sorry if my question sounds silly, but I'm not quite use to the OTP way of developing an application. There seems to be something I'm not seeing in all that. We're going to develop an application that will use Riak Core, KV, Luwak and Search: We might need to create a new storage b

Setting up a project to build atop Riak

2011-11-26 Thread Mathieu D'Amours
Hi all, I'm sorry if my question sounds silly, but I'm not quite use to the OTP way of developing an application. There seems to be something I'm not seeing in all that. We're going to develop an application that will use Riak Core, KV, Luwak and Search: We might need to create a new storage back