- Refactored the throttle module. Patch by Jeremy and me.

  * There are only two throttle levels instead of 5, namely 'enabled' and 'disabled'.  This makes it a _lot_ easier to predict when the throttle will kick in.  However, if you maintain a module that is throttle-aware, it needs to be updated!

  * The throttle mechanism now uses the current number of anonymous users or the current number of authenticated users to kick in.  This is a _lot_ more intuitive than the old throttle mechanism.

  * The throttle block has been removed -- you can now use the "Who's online" block to determine the good throttle settings.

  * Most of the documentation has been removed because it was deprecated.

  * It's less code!

1 files changed, 1 insertions, 1 deletions

diff --git a/includes/module.inc b/includes/module.inc
index 543c51057..e4ac60dda 100644
--- a/includes/module.inc
+++ b/includes/module.inc
@@ -59,7 +59,7 @@ function module_list($refresh = FALSE, $bootstrap = FALSE) {
         // Determine the current throttle status and see if the module should be
         // loaded based on server load. We have to directly access the throttle
         // variables, since throttle.module may not be loaded yet.
-        $throttle = ($module->throttle && variable_get('throttle_level', 0) > 4);
+        $throttle = ($module->throttle && variable_get('throttle_level', 0) > 0);
         if (!$throttle) {
           $list[$module->name] = $module->name;
           module_set_filename($module->name, $module->filename);