Closed (fixed)
Project:
Lost & found issues
Component:
usability
Priority:
Minor
Category:
Bug report
Assigned:
Reporter:
Created:
4 Aug 2004 at 17:48 UTC
Updated:
12 Nov 2007 at 22:41 UTC
Jump to comment: Most recent
The module selection screen currently has the headers:
------------------------------------------
| name | description | status | throttle |
------------------------------------------These are pulled straight out of the database schema.
The following would make much more sense to newbies:
--------------------------------------------
| name | description | enabled | throttled |
--------------------------------------------Patch is attached.
(I'm not sure "throttled" is very good either, but it's a term used everywhere else, so at least it's consistent. I guess if we want to change that, we should file a different bug. How about "rate limited" or "flood protected"?)
| Comment | File | Size | Author |
|---|---|---|---|
| module_selection_headers.patch | 730 bytes | al |
Comments
Comment #1
Stefan Nagtegaal commentedI think the 'throttle'/'throttled' part should only be displayed when the throttle.module is enabled and _not_ by default.. I know the checkboxes are marked as disabled, but it's kind a confusing..
Comment #2
jeremy commentedI don't think that "throttled", "rate limited" and "flood protected" are descriptive of the functionality provided by the throttle module. The congestion control provided by this module is accomplished by automatically disabling things such as modules, blocks, images, etc when a site comes under a heavy load.
Changing "enable" to "enabled" makes some sense, as when a module is checked it is enabled.
Changing "throttle" to "throttled" does not makes sense, as when a module is checked it is not throttled -- it simply is eligible to be throttled should your site come under an abnormally heavy load.
For a better understanding of this module, read this document.
If trying to replace "throttle" with a better word, it should mean "automatically disable this module when my site becomes so extremely busy that I need to temporarily conserve on CPU usage." (BTW: The blocks administration page also uses the word "throttle".)
Comment #3
cosmicdreams commentedThe organization of modules and the implementation of the throttle module has changed in the time that has past since this post. Please revisit this issue.
Comment #4
cosmicdreams commentedComment #5
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.