Re: [Semediawiki-user] Flexible #ask cache control

[Brian <Bri...@co...>]

Caches are alread invalidated upon page save - is this not what you mean?

On Thu, Jan 29, 2009 at 11:06 AM, Daniel Friesen <dan...@te...>wrote:

> Also, rather than actually disabling the cache, it may actually be
> better to setup a onedit hook that will invalidate select pages whenever
> an edit is made.
>
> ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com]
> -Nadir-Point (http://nadir-point.com)
> -Wiki-Tools (http://wiki-tools.com)
> -MonkeyScript (http://monkeyscript.nadir-point.com)
> -Animepedia (http://anime.wikia.com)
> -Narutopedia (http://naruto.wikia.com)
> -Soul Eater Wiki (http://souleater.wikia.com)
>
>
>
> Brian wrote:
> > Caching has real performance benefits. I can't imagine disabling it. I
> just
> > did some timing test on a documentation page using FireBug:
> >
> >    - 1.7 seconds for the cached verison
> >    - 16.8 seconds for the ?action=purge version.
> >
> > Ideally I could set the cache for this page to never become invalid, and
> set
> > the cache for other ask queries such as an rss feed to always be invalid.
> >
> > On Thu, Jan 29, 2009 at 9:12 AM, Yaron Koren <ya...@gm...> wrote:
> >
> >
> >> Well, "an rss feed that never changes" is an exaggeration; even cached
> >> pages get refreshed at least once a day or so, from my experience. But
> if
> >> you don't want caching for queries, you could try disabling caching on
> your
> >> wiki altogether - I don't think it's the huge performance hit some
> people
> >> consider it to be.
> >>
> >> -Yaron
> >>
> >> On Wed, Jan 28, 2009 at 8:03 PM, Brian <Bri...@co...>
> wrote:
> >>
> >>
> >>> I seem to have two very different uses of #ask. The first is
> documentation
> >>> pages which contain many demonstration #ask queries whose parser caches
> >>> should essentially never become invalid. The second is dynamic #ask
> queries
> >>> that should be reparsed every single time the page is loaded. I am
> surprised
> >>> that I have not yet found a way to achieve the latter functionality
> given
> >>> that format=rss is available. What is the point of having an rss feed
> that
> >>> never changes?
> >>>
> >>> I have come up with two potential solutions to this (assuming no one
> here
> >>> knows a way to do it with existing tech):
> >>>
> >>>
> >>>    1. An extension that creates the __NOCACHE__ magic keyword which
> then
> >>>    calls $parser->disableCache() for a given article.
> >>>    2. Adding disablecache=1 parameter to #ask
> >>>
> >>>
> >>> I have seen this implemented before in the BugzillaReports extension.
> It
> >>> doesn't look too painful:
> >>>
> >>>                 if ($this->query->get("disablecache") != null) {
> >>>
> >>>>                         #
> >>>>                         # Extension parameter take priority on disable
> >>>> cache configuration
> >>>>                         #
> >>>>                         if ($this->query->get("disablecache") == "1")
> {
> >>>>                                 $this->disableCache();
> >>>>                         }
> >>>>
> >>>>
> >>> Any thoughts on this? I think it's a pretty major issue!
> >>>
> >>> /Brian
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> This SF.net email is sponsored by:
> >>> SourcForge Community
> >>> SourceForge wants to tell your story.
> >>> http://p.sf.net/sfu/sf-spreadtheword
> >>> _______________________________________________
> >>> Semediawiki-user mailing list
> >>> Sem...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
> >>>
> >>>
> >>>
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by:
> > SourcForge Community
> > SourceForge wants to tell your story.
> > http://p.sf.net/sfu/sf-spreadtheword
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Semediawiki-user mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>