1. 26 Mar, 2007 4 commits
  2. 15 Mar, 2007 1 commit
  3. 14 Mar, 2007 1 commit
  4. 12 Mar, 2007 3 commits
  5. 02 Mar, 2007 1 commit
  6. 27 Feb, 2007 1 commit
  7. 11 Feb, 2007 1 commit
  8. 07 Feb, 2007 1 commit
  9. 31 Jan, 2007 1 commit
  10. 14 Jan, 2007 1 commit
  11. 13 Jan, 2007 1 commit
  12. 30 Dec, 2006 1 commit
  13. 22 Nov, 2006 1 commit
  14. 21 Nov, 2006 1 commit
  15. 08 Nov, 2006 1 commit
  16. 03 Aug, 2006 2 commits
  17. 14 Jul, 2006 2 commits
  18. 22 Jun, 2006 1 commit
  19. 07 May, 2006 1 commit
  20. 24 Apr, 2006 1 commit
  21. 22 Apr, 2006 1 commit
  22. 12 Apr, 2006 1 commit
  23. 08 Jan, 2006 1 commit
  24. 29 Nov, 2005 1 commit
  25. 26 Nov, 2005 1 commit
  26. 25 Nov, 2005 1 commit
  27. 06 Oct, 2005 1 commit
  28. 23 Sep, 2005 1 commit
  29. 12 Sep, 2005 1 commit
  30. 28 Aug, 2005 1 commit
  31. 14 Apr, 2005 1 commit
  32. 11 Apr, 2005 2 commits
    • Dries's avatar
      - Remove incorrect · 5b6472ef
      Dries authored
      5b6472ef
    • Dries's avatar
      - Patch #19298 by Jeremy: loose caching! · e3d62d90
      Dries authored
      Drupal's existing caching mechanism doesn't perform well on highly dynamic websites in which the cache is flushed frequently. One example is a site that is under attack by a spambot that is posting spam comments every few seconds, causing all cached pages to be flushed every few seconds.  Loose caching immediately flushes the cache only for specific users who have modified cached data (whether or not they are logged in), delaying the flushing of data for other users by several minutes.
      
      (I rewrote the help text a bit and made minor changes to the code comments.)
      e3d62d90