[development] Why do filter cache entries expire 24 hours after last cron?

[Gerhard Killesreiter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Steve Dondley schrieb:
> I'm putting together an overview of Drupal's various caching
> mechanisms. I'd like to put the answer to this question in there.

Filtered items are expired in order to keep the filter cache from
outgrowing your hard disk. Since Drupal's filter is "dumb" in the sense
that it doesn't know on which node the filtered item depends, this is
the only way to make sure the cache isn't full of old data. On
drupal.org I've modified this to keep the cached items for 48 hours.
Last time I looked the cache table had about 250k entries.

Cheers,
	Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH8Jhyfg6TFvELooQRAnJgAJ9Ct4Qc6I+BMq5rLNteO05XI3ZGfgCfcY4a
ORoCukQjZsls/OH5Y1aH1Sg=
=jn0Y
-----END PGP SIGNATURE-----