1. 10 Aug, 2009 1 commit
  2. 07 Aug, 2009 1 commit
  3. 06 Aug, 2009 1 commit
    • Tollef Fog Heen's avatar
      Reinstate svn_version code · 31484475
      Tollef Fog Heen authored
      Reinstate code to embed the svn version (or git commit id) in the
      output given by varnishd -V.
      
      Also, make sure we don't overwrite version.c when the tree is
      exported, but generate it if it's completely missing.  (This should
      only happen if somebody does svn export rather than make dist, but
      some people might do that.)
      
      git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4175 d4fa192b-c00b-0410-8231-f00ffab90ce4
      31484475
  4. 04 Aug, 2009 2 commits
  5. 03 Aug, 2009 1 commit
  6. 31 Jul, 2009 1 commit
  7. 30 Jul, 2009 1 commit
  8. 29 Jul, 2009 2 commits
  9. 28 Jul, 2009 4 commits
  10. 27 Jul, 2009 2 commits
  11. 01 Jul, 2009 2 commits
  12. 22 Jun, 2009 4 commits
  13. 21 Jun, 2009 3 commits
  14. 18 Jun, 2009 2 commits
  15. 17 Jun, 2009 2 commits
  16. 14 Jun, 2009 2 commits
  17. 13 Jun, 2009 1 commit
  18. 11 Jun, 2009 1 commit
  19. 10 Jun, 2009 2 commits
  20. 09 Jun, 2009 1 commit
    • Poul-Henning Kamp's avatar
      Remove the vcl_timeout{} VCL callback. · 236e1950
      Poul-Henning Kamp authored
      We had big plans for this originally, but none of them have materialized
      because there are better ways to do those things.
      
      For instance: why invent a lot of code to do prefetch, when wget(1) can
      do the job already ?
      
      Getting rid of vcl_timeout{} (and vcl_discard{}, see yesterdays commit)
      simplifies the expiry codes locking and statekeeping significantly.
      
      
      
      git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4100 d4fa192b-c00b-0410-8231-f00ffab90ce4
      236e1950
  21. 08 Jun, 2009 1 commit
    • Poul-Henning Kamp's avatar
      Remove the vcl_discard{} facility, it does not seem to bring benefits · b1fe4dfd
      Poul-Henning Kamp authored
      which outweigh the trouble it causes.
      
      The original idea was to allow intelligent purging for space reason
      in a size-constrained storage.
      
      In practice, storage is seldomly constrained.
      
      In the cases where it is, I have yet to see any documented benefit
      from using vcl_discard{}, likely because of the fragmentation such
      use would cause.
      
      The implementation of the vcl_discard callback had severe costs in
      code complexity (not fully unrolled by this commit) and locking
      activity.
      
      The straw that breaks the camels back, is that faithfull implementation
      of vcl_discard{} in -spersistence would force us to relocate objects,
      at a cost likely higher than picking them up from the backend.
      
      
      
      git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4099 d4fa192b-c00b-0410-8231-f00ffab90ce4
      b1fe4dfd
  22. 06 Jun, 2009 3 commits