Thu, 09 Apr 2026 17:42:28 +0000 https://bugs.horde.org/ticket/11680 Kolab Storage: serialize/unserialize handling Hi Gunnar, I'm not sure how the serialize/unserialize handling is done in Kolab_Storage. Let's take Storage/Cache/Data.php as an example. The code in store() looks like this: --------------------------------------------------- $this->_data[self::STAMP] = serialize($stamp); --------------------------------------------------- The _load() code does nothing special to the "self::STAMP" field. The getStamp() code looks like this: ---------------------------------------------- public function getStamp() { $this->_checkInit(self::STAMP); return $this->_data[self::STAMP]; } ---------------------------------------------- Is there some recursive unserialize magic happening I don't see yet? IMHO if you call getStamp(), it will return garbage. The same code pattern applies to a few other spots. OTOH the actual user of "Storage/Cache/Data.php" is "Storage/Data/Cached.php". That one unserializes the stamp before using it. Is this a performance optimization to move unserialize() to the calling side? Thomas Fri, 09 Nov 2012 15:43:28 +0000 https://bugs.horde.org/ticket/11680#t74654 While this is undeniably broken and certainly not intended: The deserialization currently happens in Horde/Kolab/Storage/Data/Cached.php on line 228. This issue will be fixed when I finished the redesign of the data area. Horde 6.0 though as this is an API change. Thu, 22 Nov 2012 18:55:31 +0000 https://bugs.horde.org/ticket/11680#t74979