I agree... but it's not a politically correct thing to say. ;-) There were people around in the 50s and 60s doing smart stuff in memory constrained environments. I have heard of research papers from that time frame being referenced for work now. It's very retro. Though under the radar, thankfully it isn't completely unappreciated.<br>
<div class="gmail_quote">On 9 March 2012 20:29, Jon Brisbin <span dir="ltr"><<a href="mailto:jon@jbrisbin.com">jon@jbrisbin.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
<div class="im"><br>
<br>
> >> If you are pushing around binary, what's the method of providing<br>
> >> an<br>
> >> identity to Riak via a message?<br>
> > You can either let it use the exchange name as the bucket and the<br>
> > routing key as<br>
><br>
> the Riak key, or you can specify them in a message header<br>
> (X-Riak-Bucket and X-Riak-Key respectively).<br>
><br>
><br>
> which rabbit tag do "X-Riak-Bucket" and "X-Riak-Key" these fit<br>
> inside?<br>
<br>
<br>
</div>If using the Java client, you'd pass in arbitrary headers using the "AMQP.BasicProperties.Builder.headers(Map)" method: <a href="http://bit.ly/A4CWu3" target="_blank">http://bit.ly/A4CWu3</a><br>
<br>
In Ruby, you'd pass them on the publish: "exchange.publish(msg, :headers => { "X-Riak-Bucket" => "foo", "X-Riak-Key" => "fookey" })"<br>
<div class="im"><br>
<br>
> > Last time I explored this BerkeleyDB was the solution...<br>
> > now I don't know the space well enough to form a solid opinion.<br>
><br>
><br>
> It has been a while, then! Things are much different in some ways and<br>
> not so much in others. How's that for an informative answer? ;)<br>
><br>
> really really helpful. Once there was "internet time", are you<br>
> measuring in NOSQL-time? In normal time, not that long. ;-)<br>
<br>
<br>
</div>Yes, NoSQL time is like dog years, only in months. So 7 months in NoSQL time is like 7 years anywhere else! :)<br>
<br>
That said, there's lots and lots of things that haven't changed in 30 years. When you get down to it, it's still a key/value lookup and some things are very similar to what we were doing many years ago writing COBOL programs on CICS/mainframes. A few years ago, I worked pretty closely with some RPG programmers (AS/400) and they were pretty frustrated with our boss, who was trying to get them to learn to embed SQL into their programs (which they really hated...can't say as I blamed them...it was much uglier and didn't work as well as using a "set lower limit" and CHAIN) and just about the time they're starting to get the hang of that, I started talking about using NoSQL in our apps and they rightly recognized that that's exactly what they'd been doing for decades!<br>
<br>
The new kids think this stuff is all flashy and fancy and uber-modern and us old fogeys (that is, those of us just barely over 35 ;) see this as somewhat of a cyclic return to a simpler and more effective way to handle data that isn't altogether different from what it was like when we first started writing PC apps using FoxPro and dBase. :)<br>
<div class="HOEnZb"><div class="h5"><br>
Thanks!<br>
<br>
Jon Brisbin<br>
<a href="http://about.me/jonbrisbin" target="_blank">http://about.me/jonbrisbin</a><br>
</div></div></blockquote></div><br>