make 'force' urls work properly
#54
Closed
opened 9 years ago by mbutterick
·
4 comments
Loading…
Reference in New Issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
Seems to not actually force a refresh as advertised.
A cache-invalidation problem.
Problem is invalidation depth. The idea of
force
is that everything on the page — and therefore everything the page depends on — would get reloaded. So theforce
signal needs to propagate through the calling chain (perhaps as a parameter) to prevent cached copies from being used.Abandoned as useless.
The
force
URL was never going to work properly because it required temporary invalidation of two caches: the render cache (for output files) and the compile cache (for input files).Instead I added a
world:current-render-cache-active
that if#f
will always regenerate a new output page. When used in combination with the existing ``world:current-compile-cache-active(i.e., when both are
#f`) the result is that every page is completely regenerated when it is requested through the project server.This is more of a blunt instrument, but because these settings can be changed easily in the
pollen.rkt
, it's OK (the idea offorce
predated the implementation of configurable project values.)