On 7/28/06, <b class="gmail_sendername">Paul T</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>3. key_salt is stored in memcached forever.</blockquote><div><br>
The problem I see with this approach is that when the salt *does* get
lost (node reboot, failure, etc), you risk that old data may be
In this case, I think that it's better to trade some efficiency for
data integrity by including the salt in the value instead of the key.
It will result in more lookups, but losing the salt won't cause issues.
The scalability in this area makes sure that any performance loss won't
be of the painful kind.<br>