[cvs] [Wiki] changed: BCBreakingHordeIssues

[Chuck Hagenbuch]

chuck  Tue, 29 Apr 2008 00:19:53 -0400

Modified page: http://wiki.horde.org/BCBreakingHordeIssues
New Revision:  2.56
Change log:  note about using expired cache data and stampede protection

@@ -26,8 +26,11 @@
 * Use exceptions instead of PEAR_Errors.
 * Clean up Horde::loadConfiguration() mess.
 * Clean up VFS_sql to use '/' as the root of the VFS instead of ''.  This
will make it behave like the other VFS backends without code to do the
conversion.
 * Set the cache expiration time when the entry is set.  This is done in 3.2
but the API should be modified to remove the $lifetime argument from get()
and exists().  When checking for cache data the check should only be that
the data is not expired.  Garbage collection should automatically remove
expired data.
+
+>> However, it's useful to have a way to use expired data in the cache, or
to have other kinds of "stampede protection" (have the first process that
hits an expired entry touch() it before regenerating it, so that other
processes don't *also* try and regenerate it - thus the stampede effect).
--ChuckHagenbuch
+
 * Don't let Horde_Crypt_pgp methods check for secure connection.
 * Remove pref_api BC files
 * Fix Horde_Cache_file:: to accept mixed $data, instead of just a string.
 * Use file_put_contents() exclusively.