[Tickets #10072] Re: Memcache storage is duplicating the key prefix

bugs at horde.org bugs at horde.org
Mon May 16 21:52:13 UTC 2011


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10072
------------------------------------------------------------------------------
  Ticket             | 10072
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Memcache storage is duplicating the key prefix
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-05-16 21:52) wrote:

> I don't say that memcache is not working correctly, im just saying  
> that i think there's some problem with it. The way i see it having  
> in the memcache something like:
> PREFIX_number_of_session

This key would be created by something that *directly* calls Horde_Memcache.

> PREFIX_PREFIX_number_of_session

This key would be created by something that calls Horde_Cache->memcache.

So these are two completely different calls.

If you are using something like memcache caching of session  
information, this is completely expected.  The session handler caches  
using direct queries to Horde_Memcache.  But that same data may be  
cached elsewhere via Horde_Cache.  So although the data happens to be  
the same, it is not a duplicate key - they are two independent keys  
that happen to have the same data.  As mentioned previously, this is  
an inevitable limitation of OO programming (and caching in general).






More information about the bugs mailing list