Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion getting rid of AS::Cache::Entry in the memcached store
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Xavier Noria  
View profile  
 More options Sep 23 2012, 11:20 am
From: Xavier Noria <f...@hashref.com>
Date: Sun, 23 Sep 2012 17:19:39 +0200
Local: Sun, Sep 23 2012 11:19 am
Subject: Re: [Rails-core] Re: getting rid of AS::Cache::Entry in the memcached store

On Sat, Sep 22, 2012 at 11:42 PM, Xavier Noria <f...@hashref.com> wrote:

On Sat, Sep 22, 2012 at 10:55 PM, Michael Koziarski
<mich...@koziarski.com>wrote:

>  I disagree very strongly with this line of reasoning.  If you're using
>> memcached as a cache store, you should be relying on its semantics,  which
>> is that nil and 'no value' are identical.

> Basing the store on that premise seems sound to me.

I have checked the memcache binary protocol and memcache does tell you if a
key is not known. Wouldn't dalli be the one not following the semantics
here?

If I understand everything correctly we could theoretically use a different
client that provides that interface and allow us to cache nil values. Not
claiming such client exist, only digging into where is the real problem
regarding nil.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.