A very interesting hook would be to be able to send a message to a queue
whenever siblings are created. With such a hook, you could have business logic
somewhere trying to resolve the conflict. Unfortunately, that's not easy
because siblings can be created at other places than PUT; namely when
On Apr 20, 2011, at 3:01 PM, Mark Phillips wrote:
> Thanks, Jon. This is great stuff!
>
> In case anyone is interested, I took the liberty of putting all the
> Riak + RabbitMQ code in one section on the wiki:
>
> http://wiki.basho.com/Community-Developed-Libraries-and-Projects.html#Riak-and-Rab
Thanks, Jon. This is great stuff!
In case anyone is interested, I took the liberty of putting all the
Riak + RabbitMQ code in one section on the wiki:
http://wiki.basho.com/Community-Developed-Libraries-and-Projects.html#Riak-and-RabbitMQ
(I debated calling it the "Riak and Jon Brisbin" section
I've been carrying this evented datastore torch for a while now and been making
pretty good progress in that direction. This evening I pushed a Riak postcommit
hook to my github that sends updated entries to RabbitMQ using the Erlang AMQP
client.
https://github.com/jbrisbin/riak-rabbitmq-commit
