Hi James and Jeroen,
Would you pleaes explain what is being gained
by query caching? It seems to me that simple transclusion of pages
stored on wikidata would be just as effective, would require no
additional code. Thanks for your reply - john
On 26.07.2012 12:12,
Jeroen De Dauw wrote:
> Hey James,
>
> This implementation of you is
great, but there are some important differences with having full query
management functionality.
>
> Your solutions is great because:
>
> *
It's very simple
> * It has huge benefits for API and Special:Ask
queries
>
> While the thing I'm proposing
>
> * Is complex
> * Does
not benefit the API and Special:Ask (since it would consciously ignore
these to avoid doing not needed work)
>
> But then again, it solves
another problem then your change:
>
> * it fixes the existing
persistent MediaWiki cache for articles to get invalidated at the
correct points
> * and it persistently caches results for inline
queries
>
> So these two caching solutions can live happily next to
each other. Once the new one has been implemented I suggest disabling
the current one for inline queries, but keeping it for all the rest.
>
> Cheers
>
> --
> Jeroen De Dauw
> http://www.bn2vs.com [1]
> Don't
panic. Don't be evil.
> --
Links:
------
[1] http://www.bn2vs.com
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
