D. Berge 2733223037 Refresh the log more aggressively.
On the backend, the events endpoint caches responses
by ETag in order to reduce the load on the database
and response times. That cache is supposed to be
invalidated with the middleware receives a notification
that the underlying data has changed. However, that
change might arrive just *after* the HTTP request,
meaning that if we let the browser do its thing we
will probably be returning stale data.

So what we do is we explicitly request a non-cached
response when we know that something has changed
because we changed it ourselves.

What we do not do is bypass the cache if we receive
a change event notification, as we assume that the
HTTP roundtrip will be more than sufficient for
the server to have invalidated (and perhaps even
refreshed) its response.
2020-09-29 00:30:40 +02:00
2020-08-24 21:01:47 +02:00

Dougal Seismic production & data analysis tool

Structure of this repo

  • bin/ Scripts that import / export data into / out of the database.
  • etc/ Configuration files.
  • lib/ Code files.
    • lib/www/ Web interface and API.
      • lib/www/client/ Frontend.
      • lib/www/server/ Backend.
  • sbin/ System maintenance scripts.
Description
No description provided
Readme 11 MiB
Languages
Vue 41.7%
JavaScript 32.3%
PLpgSQL 16.5%
Python 5.4%
Nunjucks 3.2%
Other 0.9%