Re: upcoming changes to TTLs.

On 1996-10-28T09:58:11,
   wessels@nlanr.net (Duane Wessels) said:

> lmb@pointer.in-minden.de suggested the same thing.

Yes, I was quite amused when his and mine mail arrived at about the same
time here ;-)

> How would you like to specify this in the config file? global option?
> stuff it in the refresh_pattern line? what are the parameters?

Your current proposal was:

The 'ttl_pattern' config option is replaced with a 'refresh_pattern'
directive. In addition to the regular expression, the refresh_pattern
line takes three parameters: min, max, percent.

I would probably stuff this in the refresh_pattern line as a time relative
to the LM. If the object has been more than this time in the cache already,
issue an asynchronous IMS.

And of course, if the IMS fails because there is an error, the request
should be issued again later. (I ask for this because I am not always
connected to the Net - if you don't implement this, no problem ;)

And there probably should be an option to not only issue this Async-IMS when
the object is requested, but in the background, by periodically checking if
the objects should be IMSed. I could also see a use for an option to not
periodically checking all objects, but for explicitly invoking this check,
perhaps in the night when there is more free bandwidth.

-- 
Lars Marowsky-Bree   Voice: +49-571-63663   PGP-key avail. via server
HomePage: http://www.teuto.de/~lmb/    Mail: lmb@pointer.in-minden.de
PGP-Id: 0xDAB57941 / CF FC 3A F0 86 F1 D3 EB  79 8A CF 75 4F 4C 81 DF
     < to prevent forgery, all email by me is signed with PGP >