Closed (works as designed)
Project:
Memcache API and Integration
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Nov 2009 at 17:29 UTC
Updated:
26 Apr 2010 at 19:50 UTC
Looking at the dmemcache_key function it uses the Drupal cid to create the memcache key. As a result since Drupal's cid on cache_page and cache_block contain the fully qualified URL of the request it's possible in some situations, especially some load-balanced situations that the same cache is being used by servers with different fully qualified URLS.
It seems like there should be some way of using the request path instead of the fully qualified URL to make the cache more efficient since there is the ability to explicitly prefix the key if multi-site behavior is desired.
Comments
Comment #1
mbutcher commentedThis would be a good thing, right?
First, it means you can use multi-site and Domain Access in conjunction with caching -- a definite must.
Second, it means that multiple servers can use the same cache so long as their hostname is the same -- the typical configuration on a load-balancer.
Comment #2
jeremy commentedAgreed, this is by design.