On 3/10/2010 5:46 PM, moses wejuli wrote:
it's not so much a /"theoretically reliable storage mechanism"/ but only storing data for as long as the programmer chooses or in this case, for only as long as the user is logged on (data is expelled when the user chooses to log out or is forcibly logged out for one reason or another).
Or until any component fails, needs a change, etc.
data miscalculation? i think you'd have to take care as a /dev/ for this not to happen -- infact this is presently the case (think max slab size)
I'd guess that it's uncommon for memcache users to have any idea how many potential keys might be in use at once (constructing them from arbitrary sql queries, etc.). Or to do anything to remove data. You really can't iterate over it to see what needs to be removed - and where else would you store the keys so you'd know about them?
-- Les Mikesell lesmikes...@gmail.com
