In pm-london, you wrote:
>> Instead of (or perhaps as well as) a MAXAGE parameter, why not
>> have an EXPIRES parameter which takes similar values to an HTTP
>> expires header?
>
><sane>
>This got me thinking that you might also want to set something to be
>another value when it times out. So you might want to set it to say, '10'
>or a nice user friendly string 'No longer valid'.
>
>Or you might want to tie the previous value so that your scalar returns to
>it's orignal value after a while.
></sane>
>
><mildlyInsane>
>Then I got thinking even more and decided that you might want to have a
>whole host of values, so maybe you want to to pass it a ref to a sub that
>could compute values. For example, you could use it to store the IP of a
>domain name and have it automagically request a new one after some
>predefined time period so that you that your long living server copes
>with a domain name changes but still caches...
></mildyInsane>
Both these ideas will be addressed via another parameter you can pass to
tie(), namely
POLICY => sub { ... },
with a default of
POLICY => sub { undef }
Marcel
--
We are Perl. Your table will be assimilated. Your waiter will adapt to
service us. Surrender your beer. Resistance is futile.
-- London.pm strategy aka "embrace and extend" aka "mark and sweep"
