|
|
|
| laziness, impatience, and hubris | |
| PerlMonks |
Re: Re^3: Renovating Best Nodes (custom nodelets)by demerphq (Chancellor) |
| on Feb 13, 2004 at 18:35 UTC ( [id://328850]=note: print w/replies, xml ) | Need Help?? |
|
I'm pretty sure you'll not get user preferences in the nodelets for quite a while (if ever). Nodelets are rendered on every page load and so are best when they can be cached. And cached nodelets can't be user-specific. Yep. When i wrote that reply I hadn't realized the implications of the node caching on what I was saying. In fact I _keep_ forgetting them. Your caching for best/worst nodes is quite nice but it still reads quite a few records out of the database. Doing that 4 times for every page load would probably end up with more DB load than we had before your work. I agree totally. Would it be too much (in terms of policy etc) to make small versions of the various nodelets? With say 5 lines in each, and a link to their respective full page version?
---
demerphq First they ignore you, then they laugh at you, then they fight you, then you win.
In Section
Perl Monks Discussion
|
|
|||||||||||||||||||||||||||