On Sat, Sep 22, 2012 at 11:42 PM, Xavier Noria <[email protected]> wrote:
On Sat, Sep 22, 2012 at 10:55 PM, Michael Koziarski <[email protected]>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 received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
