grant.maxwell at maxan.com.au
Thu Jun 12 23:47:38 UTC 2008
thanks for the thoughts Brian
I have thought of a way to do this for our case.
You see Brian the restart situation/node going down is already taken
care of. It's only a problem if the class record exists but the item
record does not.
The way to deal with this is to write them all to the cache as a
single object (perl hash list probably). That actually delivers
exactly the guarantee we need. And it's really simple.
It also saves me going out to look at other products - I like memcached.
cheers folks - case closed :)
And thanks for all the input.
On 13/06/2008, at 1:39 AM, Brian Moon wrote:
>> So we need to know that if we add the class and it's records, they
>> to stay. Otherwise we could block actions because a record was not
>> - for whatever reason.
> This all still falls apart when you are talking about a volitale
> cache, IMO. What happens when a memcached node goes down? You have
> to plan for that.
> It just does not sound like memcached is a good match for what you
> are trying to do.
> Brian Moon
> Senior Developer/Engineer
> When you care enough to spend the very least.
More information about the memcached