We've implemented essentially this approach to namespaces in PHP here at IMVU (we call them a cache-class). It works great - we set very long timeouts on most of our queries, and still give our users instant feedback when the underlying data changes.
<br><br>I've blogged about our implementation <a href="http://www.imvu.com/blogs/index.php?blog=793&title=extensions_to_php_memcached_api">here</a> and included a zip file containing our implementation for others to use.
<br><br>Chris<br><br>-- <br><a href="http://www.imvu.com/technology">http://www.imvu.com/technology</a><br><br><div><span class="gmail_quote">On 7/28/06, <b class="gmail_sendername">Serhat Sakarya</b> <<a href="mailto:serhat@sakarya.nl">
serhat@sakarya.nl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><span class="q">On 7/28/06, <b class="gmail_sendername">
Paul T</b> <<a href="mailto:pault12345@yahoo.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">pault12345@yahoo.com</a>> wrote:</span></div><div><div></div><div><span class="q"><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></span></div><div><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
revalidated.<br>
<br>
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>
</div><br>
Regards,<br>
<br>
Serhat</div>
</div></blockquote></div><br><br clear="all"><br><br>