On Apr 18, 2011, at 5:35 PM, Wilson MacGyver wrote:
> On Mon, Apr 18, 2011 at 6:12 PM, Jon Brisbin wrote:
>>
>> If true atomicity is really a concern, then use Redis and write a pub/sub
>> handler to update your Riak documents whenever things change.
>>
>> You know we could probably take the
On Mon, Apr 18, 2011 at 3:12 PM, Jon Brisbin wrote:
>
> On Apr 18, 2011, at 2:47 PM, Ben Tilly wrote:
>
>> The first is that I've heard that there is a limit to the size of the
>> headers that can be sent using the http interface and therefore the
>> number of links that you can use. Is this true
On Mon, Apr 18, 2011 at 6:12 PM, Jon Brisbin wrote:
>
> If true atomicity is really a concern, then use Redis and write a pub/sub
> handler to update your Riak documents whenever things change.
>
> You know we could probably take the Riak RabbitMQ postcommit hook and adapt
> it to use Redis for
se dw settings.
Also, don't do use riak for applications that need locks.
Cheers. Alexander.
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Ben Tilly
Sender: riak-users-boun...@lists.basho.com
Date: Mon, 18 Apr 2011 12:47:28
To:
Subject: Random questions
The fir
On Apr 18, 2011, at 2:47 PM, Ben Tilly wrote:
> The first is that I've heard that there is a limit to the size of the
> headers that can be sent using the http interface and therefore the
> number of links that you can use. Is this true, and if so does anyone
> know what the limit is?
I suppose
The first is that I've heard that there is a limit to the size of the
headers that can be sent using the http interface and therefore the
number of links that you can use. Is this true, and if so does anyone
know what the limit is?
My second question is this. It seems that if accesses are config
