Summary | display_tasklists is saved on every page access |
Queue | Nag |
Queue Version | Git master |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | slusarz (at) horde (dot) org |
Created | 09/03/2010 (5419 days ago) |
Due | |
Updated | 09/23/2010 (5399 days ago) |
Assigned | 09/22/2010 (5400 days ago) |
Resolved | 09/23/2010 (5399 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
2010-09-22T00:39:08-06:00 DEBUG: HORDE [nag] Horde_Prefs: Storing
preference value (display_tasklists) [pid 30516 on line 257 of
"/disk2/src/horde/framework/Prefs/lib/Horde/Prefs.php"]
triggered. :)
be updated every page load. Even if the value isn't changing, we
shouldn't be wasting time recreating at all. At a minimum, this
really needs to be cached (see, e.g., caching IMP's folder tree using
session caching as a fallback if no Cache system is available).
probably see this because of the Copy/Move to Tasklist feature.
Request #9219: Move pref saving logging to a more appropriate locationhttp://git.horde.org/diff.php/framework/Prefs/lib/Horde/Prefs.php?rt=horde-git&r1=77e3dd782f525dadbb88512854d903ac2d7f9cb9&r2=b4a73fd1a465e79c3be80e12e225f7cc6c268dcd
2010-09-22T00:39:08-06:00 DEBUG: HORDE [nag] Horde_Prefs: Storing
preference value (display_tasklists) [pid 30516 on line 257 of
"/disk2/src/horde/framework/Prefs/lib/Horde/Prefs.php"]
triggered. :)
be updated every page load. Even if the value isn't changing, we
shouldn't be wasting time recreating at all. At a minimum, this
really needs to be cached (see, e.g., caching IMP's folder tree
using session caching as a fallback if no Cache system is available).
probably see this because of the Copy/Move to Tasklist feature.
State ⇒ Assigned
2010-09-22T00:39:08-06:00 DEBUG: HORDE [nag] Horde_Prefs: Storing
preference value (display_tasklists) [pid 30516 on line 257 of
"/disk2/src/horde/framework/Prefs/lib/Horde/Prefs.php"]
As someone who never uses nag, I have no idea why this needs/should be
updated every page load. Even if the value isn't changing, we
shouldn't be wasting time recreating at all. At a minimum, this
really needs to be cached (see, e.g., caching IMP's folder tree using
session caching as a fallback if no Cache system is available).
State ⇒ Feedback
time. But the prefs library is only saving it when the preference
value changed. Are you saying this check doesn't work anymore, or is
the preference value really changed?
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ display_tasklists is saved on every page access
Queue ⇒ Nag
Milestone ⇒
Patch ⇒ No
State ⇒ New
every time it is run. Should be refactored to only save if tasklist
changes.
Noticed this in my logs when doing a dimp poll refresh - for some
reason, display_tasklists was being updated.
Not familiar with the code but making the assumption that
display_tasklists doesn't change on a regular basis. (If it does, it
should not be a preference at all).