Re: 1 cset was pushed to modules/stable: bug 3740 - regenerate the static/session...

Jason Judge wrote:

> 
> "Jonn Beames" <[email protected]> wrote in message
> news:[email protected]...
>> ...
>> Sure, it can be done as a scheduled task.  Everything is there to do it
>> that.  The request I keep getting is for the cache to regenerate when it
>> is invalidated by event, not time.
> 
> Then perhaps we need some kind of event queue for the schedular, so that
> one-off events can be logged with the schedular, to be run next time it
> fires up?
> 
> -- JJ

That sounds like a good idea for other problems I can envision.  Alas, the
pain in the auto regeneration of sessionless on create/update/delete is
that, if the list of URLs is long, it can take awhile, which is why the bug
got reported and I tried to make it a background process. So, in this
situation, we have...

Good: if the regeneration is dropped into the schedular queue to be fired
off on next 'get' request it would allow us to run it as a shutdown process
and flush the output to the requesting browser before commencing, so the
requester gets the page quickly and maybe doesn't realize that the
connection is still open as the process runs.

...but...

Bad: we still have all the same problems you were aluding to that make
background processes a problem: if they take a long time and are triggered
often, people will get in trouble.

I'll have to come up with some better way of managing auto-regeneration
(maybe segmenting or truncating it if takes too long), or just remove it
all together.

 - Jonn