Hi,<br><br>I am looking at implementing my own rabbit_msg_store_index that would use Redis (probably with JSON serialization<br>of Erlang data types, I need basic queue inspection capabilities and don't care much about performance degradation compared to<br>
raw ETS).<br><br>My first question is, could someone from the rabbitmq team briefly explain when each of the functions is used? insert and delete<br>are pretty self-explanatory but some others are not. This is what I am referring to:<br>
<br>behaviour_info(callbacks) -><br> [{new, 1},<br> {recover, 1},<br> {lookup, 2},<br> {insert, 2},<br> {update, 2},<br> {update_fields, 3},<br> {delete, 2},<br>
{delete_by_file, 2},<br> {terminate, 1}];<br clear="all"><br><br>My 2nd question is: I see that <a href="http://rabbit_app.in">rabbit_app.in</a> instructs rabbit to use ETS implementation. Does it mean that in order to use Redis backend I'd have<br>
to build rabbit from source and build my own .deb packages? or is there a way to do this from a "regular" dynamically loaded plugin?<br><br>Thank you.<br><br>-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br>
<a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br><br>