feature request cache refresh

[Rob S]

Poul-Henning Kamp wrote:
> In message <4B56D2B1.9090502 at gmail.com>, Rob S writes:
>
>   
>> Our experience of grace is that the first client who requests content 
>> after expiry is held up talking to the backend, whilst other subsequent 
>> clients get delivered the graced stale content.  But, if that's not 
>> intended, perhaps our config isn't quite right.
>>     
>
> That is indeed the correct behaviour.
>   
Great.  So, going back to my original post:

 > I'm not sure if it's best to have
 > a parameter to vary the behaviour of 'grace', or to have an additional
 > parameter for "max age of stale content to serve".


If grace stays as it is, then I'd like to have the ability for that 
"first client who requests content after expiry" to get stale content, 
and have a parallel process update the cached content.

Ro*b*