1. 06 Aug, 2020 1 commit
  2. 21 Jul, 2020 4 commits
  3. 12 Jun, 2020 3 commits
  4. 08 Jun, 2020 1 commit
  5. 04 Jun, 2020 1 commit
  6. 03 Jun, 2020 1 commit
  7. 02 Jun, 2020 2 commits
  8. 01 Jun, 2020 4 commits
  9. 18 May, 2020 2 commits
  10. 11 May, 2020 1 commit
  11. 06 May, 2020 1 commit
  12. 04 May, 2020 3 commits
  13. 01 May, 2020 1 commit
  14. 04 Mar, 2020 1 commit
  15. 03 Mar, 2020 6 commits
  16. 02 Mar, 2020 1 commit
  17. 29 Feb, 2020 1 commit
    • Leon P Smith's avatar
      Tweak cache to store raw responses · bd2f47d2
      Leon P Smith authored
      This is a little hacky;  honestly we should probably just move to a
      write-through cache, as I don't see much upside to a write-back cache
      and a couple of benefits,  even disregarding the extra code complexity.
      
      TODO:
       1. Explore the possibility of discarding the raw responses from
          in-process memory after a cache reload from the database.
          This would save some memory, though it would be a bit easier
          to accomplish with a write-through cache.
       2. General code cleanups;  this feels like a bit of mess.
       3. Of course, the primary goal of this exercise:  ensure that
          protocol constants on the public node API are served out of
          the Raw Cache,  and not after they've passed through some
          dodgy parsers.
      bd2f47d2
  18. 28 Feb, 2020 3 commits
  19. 27 Feb, 2020 3 commits