-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/14/09 3:41 PM, Peter Saint-Andre wrote: > On 4/21/09 1:36 PM, Peter Saint-Andre wrote: >> On 4/21/09 11:43 AM, Robin Collier wrote: > >>> I am somewhat surprised that the 1st item is not already part of the >>> spec, as I see it as much more desirable than max_items, the only >>> current option for limiting the volume stored. I would think that for >>> most multi user applications, determining a hard value for the number of >>> items you wish to keep would be more difficult than determining at what >>> time they are no longer relevant. >> This is typically a service-wide configuration option, not a per-node >> configuration option (e.g., the admin of your pubsub service decrees >> that nodes shall not contain items more than 30 days old as a form of >> garbage collection). Why exactly does this need to be a per-node option? > > It's still not clear to me if we need a per-node option for this, but I > suppose it's fine since we already have max_items.
In my working copy this is now the stale_time node configuration option. /psa -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkquudYACgkQNL8k5A2w/vxdpACeJzyqFx69oDMBF49wnzTGGcjV eWMAoKy1/R+jjJwi84MVGke+8pEiZWcS =3OOC -----END PGP SIGNATURE-----
