1. 18 Feb, 2019 9 commits
    • Nils Goroll's avatar
      check in new boilerplates · 55448d30
      Nils Goroll authored
      55448d30
    • Dridi Boukelmoune's avatar
      Code style · 60a70c88
      Dridi Boukelmoune authored
      This line ain't too long to be broken.
      60a70c88
    • Poul-Henning Kamp's avatar
    • Lasse Karstensen's avatar
      230aa946
    • Geoff Simmons's avatar
      Rename the obj flag OF_CHGGZIP to OF_CHGCE, for "changed Content-Encoding". · 54af42d4
      Geoff Simmons authored
      And update the comment explaining what happens. This is to make it
      apparent that a VFP has changed C-E in the stored object, so C-E
      should not be changed by an IMS fetch, and a new ETag from IMS has
      to be weakened. The flag is appropriate for use by any VFP that
      needs to manipulate C-E this way (not just gzip).
      
      Closes #2910
      54af42d4
    • Nils Goroll's avatar
      integer types consistency · ee51ce05
      Nils Goroll authored
      Thank you, @fgsch
      ee51ce05
    • Poul-Henning Kamp's avatar
      Flexelinting · 0250f758
      Poul-Henning Kamp authored
      0250f758
    • Nils Goroll's avatar
      changelog · 60670c9c
      Nils Goroll authored
      60670c9c
    • Nils Goroll's avatar
      Add bans on obj.ttl, obj.age, obj.grace and obj.keep · b06cdbba
      Nils Goroll authored
      Also add a duration argument type and the operators >, >=, < and <=
      for use with it (besides the existing == and !=).
      
      obj.ttl and obj.age are compared relative to the time the ban was
      issued, as required by the fact that bans are evaluated some arbitrary
      time after they are created. For this reason, the ban_dups parameter
      has no effect on obj.ttl and obj.age bans, duplicates of bans using
      these fields are never removed.
      
      obj.grace and obj.keep are compared as absolute values.
      
      In an effort to support The Proprietary Stevedore (tm) [or any other storage
      engine supporting persistent bans - if any?], the existing ban serialisation
      format is preserved and upgrades _should_ work seamlessly. But downgrades won't.
      
      Using the BANS_HAS_* macros, we try to make the relationship between the ban
      serialisation in cache_ban_build.c and access in cache_ban.c more obvious.
      
      We now generate all fields and operators from table files as well as
      the definition of allowed operators for fields. The user help text
      about allowed operators is generated at init time.
      b06cdbba
  2. 17 Feb, 2019 2 commits
  3. 16 Feb, 2019 1 commit
  4. 15 Feb, 2019 1 commit
  5. 14 Feb, 2019 1 commit
  6. 13 Feb, 2019 2 commits
  7. 12 Feb, 2019 2 commits
  8. 11 Feb, 2019 6 commits
  9. 08 Feb, 2019 6 commits
  10. 06 Feb, 2019 10 commits