<br><br><div><span class="gmail_quote">On 1/11/06, <b class="gmail_sendername">Matthew Glubb</b> <<a href="mailto:matt@zgroupplc.com">matt@zgroupplc.com</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;">
I simply wish to be able to delete a key that has a zero expiry<br>period and then immediately be able to add a key of the same name.<br>The reason that I cannot use set is because if it already exists in<br>the cache I do not want to replace the value.
<br></blockquote></div><br>I have a somewhat similar requirement, but I'm curious about this specific approach. It sounds as if an object may go into the cache with a given key, but in some scenarios if that key is already in use, that object would use a different key in the cache. Is that accurate?
<br><br>This sound as if you might be using the cache as a queue or something to delineate prioritization or ordering.<br><br>I know this doesn't resolve the particular add/delete/add scenario, but I'm curious about the requirements side.
<br><br>cheers,<br>j<br>