Last modified: 2011-11-29 20:21:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T2172, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 172 - Cached copies of special pages
Cached copies of special pages
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-08-19 02:56 UTC by SJ
Modified: 2011-11-29 20:21 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description SJ 2004-08-19 02:56:42 UTC
NOTE:  THIS SHOULD BE FILED UNDER "OTHER", a component which doesn't exist yet.
This is NOT a Mediazilla bug, but a lack in the interface.

Optional cached copies of watchlists should be available to users who have
checked their watchlist recently and just want to see the cached copy again.

Cached copies of frequently-requested pages like New Pages and New Users should
be similarly available - perhaps cached every minute.  In fact, these should be
the defaults for those special pages, with an up-to-the-second query available
only by following a small link (since it takes up to half a minute to retrieve
the page anyway, there's hardly a difference between the two).

I've wanted such features for a while (I may be atypical, but I *never* need an
up-to-the-second copy of these pages; a 5-min old copy would be just fine. 
Similarly, if I could turn on a "always limit me to loading my watchlist once
every 6 hours" preference, I would leave it on).  I'm filing this bug after
seeing the following comment today while jeronim was killing processes to try
and speed up the db.

[18|16:37] <jeronim> killing the newpages queries had a pretty dramatic effect
Comment 1 xmlizer 2004-08-19 09:08:27 UTC
one nice feature with the cached copies in general, is the *mention of the
generation timestamp*

Comment 2 Timwi 2004-08-19 10:39:38 UTC
It is possible to generally serve a cached page, and still have it be
up-to-date.  Just invalidate the cache whenever someone creates a new page (for
[[Special:Newpages]]) or a new account (for [[Special:Listusers]]). It should
also be possible, upon every edit, to invalidate the cache only for those watch
lists that contain it.

> NOTE:  THIS SHOULD BE FILED UNDER "OTHER", a component which doesn't exist yet.

It does exist.  It is called "General/Unknown".  And it should not be filed
there, it is perfectly in the right place under "Special pages".
Comment 3 Brion Vibber 2005-12-21 05:23:25 UTC
This is not a current issue.
Comment 4 Brion Vibber 2011-11-29 20:21:17 UTC
Going through old bugs marked LATER ...

This feels like it's resolvable by just leaving the tab open. :)

Loading watchlists etc also isn't as slow as it was back in '04, so the desire to not reload the page is likely lower than it used to be.

I'm taking the initiative to close this out; if there's a need for related ideas please reopen or file a new, more specific bug. Thanks!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links