One of our main uses for Caspar is to combine playout of a HTML-based news display with our webradio stream.
When building the display page, a lot of thought went into resilience since we rely on external RSS feeds providing content from a public webserver. After each display cycle of 10 news articles, the content is re-read (if available) and stored on a local web server, images are fetched and stored locally as well. After a browser has made the initial request for the page, there is another level of resilience. All content is fetched via AJAX calls, and if our local webserver would go offline, the content currently in cache would spin indefinitely.
On regular browsers this works fine, but Caspar does not seem to be able to cache images. When switching the server off, as soon as the next article is displayed only the text and html layout is preserved, the background image is missing.
It would be a great addition for this sort of application if Caspar could:
A. Keep a local file based cache for HTML-related content
B. Honor the different cache headers to control it, especially the fairly recent stale-while-revalidate directive.
Would this at all be possible to within the current HTML producer library, or would it require massive amounts of work to pull it off?
Lead IT technician
Ålands Radio och TV Ab