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).
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) On 10 March 2010 23:34, Les Mikesell <lesmikes...@gmail.com> wrote: > On 3/10/2010 5:14 PM, moses wejuli wrote: > >> Yes, good point as far as service interruption is concerned but I don't >> see how this affects performance, especially if the programmer carefully >> uses this feature for tiny amounts of data per user.... I just think, >> given how far memcache has metamorphosed, the time is probably right to >> include such a feature (to be used with some care of course) >> > > You can't count on nothing ever going wrong. How should this theoretically > reliable storage mechanism respond to a network glitch to one or more of the > servers? Or just a miscalculation in terms of how much data you throw at > it? > > -- > Les Mikesell > lesmikes...@gmail.com > > >
