Skip to content

V
varnish-cache
Switch branch/tag
  1. 30 Jul, 2009 1 commit
  3. 29 Jul, 2009 2 commits
  5. 28 Jul, 2009 4 commits
  7. 27 Jul, 2009 2 commits
  9. 01 Jul, 2009 2 commits
  11. 22 Jun, 2009 4 commits
  13. 21 Jun, 2009 3 commits
  15. 18 Jun, 2009 2 commits
  17. 17 Jun, 2009 2 commits
  19. 14 Jun, 2009 2 commits
  21. 13 Jun, 2009 1 commit
  23. 11 Jun, 2009 1 commit
  25. 10 Jun, 2009 2 commits
  27. 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
  29. 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
  31. 06 Jun, 2009 6 commits
  33. 03 Jun, 2009 2 commits
  35. 29 May, 2009 1 commit
  37. 26 May, 2009 1 commit