taler-deployment

Deployment scripts and configuration files
Log | Files | Refs | README

2019-06-02-exchange-caching.txt (841B)

      1 # Exchange Wire Caching
      2 
      3 
      4 ## Issue Summary
      5 
      6 When demoing Taler to an audience, sometimes withdrawing or other operations
      7 fail.  This can happen even with a fresh wallet.
      8 
      9 
     10 ## Root Cause
     11 
     12 The browser caches the /keys and /wire response for a long time, even when the
     13 wallet is re-installed.
     14 
     15 Usually the cache expiration is set to when available denominations or signing
     16 keys are expected to change.  This can be a rather long time.  We often have format changes
     17 or re-deploys with different keys in-between.
     18 
     19 ## Remediation and Prevention
     20 
     21 For demo and test, the exchange shall use shorter expiration times.
     22 (https://bugs.gnunet.org/view.php?id=5747)
     23 
     24 To force re-downloading of the exchange's information, we will implement
     25 a client-version parameter to break the browser's cache.
     26 (https://bugs.gnunet.org/view.php?id=5745)
     27 
     28 ## Discussion
     29