1. 17 Jan, 2006 1 commit
  2. 16 Jan, 2006 1 commit
  3. 05 Jan, 2006 1 commit
  4. 15 Dec, 2005 1 commit
  5. 30 Nov, 2005 1 commit
  6. 29 Nov, 2005 2 commits
  7. 27 Nov, 2005 1 commit
  8. 21 Nov, 2005 2 commits
  9. 22 Oct, 2005 1 commit
  10. 09 Oct, 2005 1 commit
  11. 19 Sep, 2005 1 commit
  12. 18 Sep, 2005 1 commit
  13. 08 Sep, 2005 1 commit
  14. 29 Aug, 2005 1 commit
  15. 25 Aug, 2005 3 commits
  16. 22 Aug, 2005 1 commit
    • Dries's avatar
      - Patch #29274 by Jeremy: the "fuzzy cache" mechanism is supposed to enforce a... · 75abab24
      Dries authored
      - Patch #29274 by Jeremy: the "fuzzy cache" mechanism is supposed to enforce a minimum time before the cache table is flushed. Logical errors in the fuzzy cache implementation are leading to the cache table being flushed more frequently.  Configuration is simplified by removing all references to "strict" and "loose" caches. Instead, the cache is either "disabled" or "enabled". Additionally, the site administrator can now configure the "minimum cache lifetime", the minimum amount of time cached data will remain cached.
      75abab24
  17. 05 Aug, 2005 1 commit
  18. 29 Jul, 2005 2 commits
  19. 27 Jul, 2005 1 commit
  20. 23 Jul, 2005 1 commit
  21. 03 Jul, 2005 1 commit
  22. 27 Jun, 2005 1 commit
  23. 22 Jun, 2005 1 commit
  24. 21 Jun, 2005 1 commit
  25. 07 Jun, 2005 1 commit
    • Dries's avatar
      · 1474632a
      Dries authored
      - Patch #24135 by Moshe: made it possible to ban visitors based on hostname/IP.  Banning visitors can either be done from the 'access control' pages, or directly from the statistics pages.  This feature is very convenient to block badly behaving crawlers.
      1474632a
  26. 21 May, 2005 1 commit
  27. 14 May, 2005 2 commits
  28. 12 May, 2005 1 commit
    • Dries's avatar
      · 2b7f504d
      Dries authored
      - Added the ability to track page generation times in the statistics module.
        (Made some improvements as per the suggestions in the issue.)
      
      - Added extended timer implementation.
      2b7f504d
  29. 12 Apr, 2005 1 commit
  30. 11 Apr, 2005 1 commit
    • 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
  31. 05 Apr, 2005 1 commit
  32. 31 Mar, 2005 2 commits
  33. 19 Mar, 2005 1 commit